From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Honggyu Kim <hong.gyu.kim@lge.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Remove duplicated include in gdb directory
Date: Tue, 07 Jan 2014 16:16:00 -0000 [thread overview]
Message-ID: <m338kz22en.fsf@redhat.com> (raw)
In-Reply-To: <20140107025701.GF3802@adacore.com>
On Tuesday, January 07 2014, Joel Brobecker wrote:
> In that spirit, we kindly request that the text of the ChangeLog
> entry be part of the email, rather than in the diff. Having it in
> the diff also is fine, I think, if it makes it simpler to send
> the patch.
Thanks for pointing that out, Joel.
Just a little obvious-rationale: the reason we request ChangeLog entries
to be posted as non-diff (i.e., as part of the e-mail) is because it
makes it easier to apply the patch without having to deal with
conflicts.
Anyway, the patch was already pushed so it doesn't really matter now
:-). And welcome aboard, indeed!
--
Sergio
next prev parent reply other threads:[~2014-01-07 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 1:13 Honggyu Kim
2014-01-07 2:12 ` Honggyu Kim
2014-01-07 2:57 ` Joel Brobecker
2014-01-07 5:07 ` Honggyu Kim
2014-01-07 16:16 ` Sergio Durigan Junior [this message]
2014-01-07 16:16 ` Sergio Durigan Junior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m338kz22en.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hong.gyu.kim@lge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox