From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA 2/4 take 2] Improved linker-debugger interface
Date: Thu, 19 Jul 2012 17:02:00 -0000 [thread overview]
Message-ID: <874np3zntp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120719110509.GC16185@redhat.com> (Gary Benson's message of "Thu, 19 Jul 2012 12:05:09 +0100")
>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:
Gary> This patch moves a block of code in solib-svr4.c. There are no
Gary> code changes. I couldn't figure out how to write a ChangeLog for
Gary> this--does it need one?
Yeah, all changes need a ChangeLog entry.
You can write something like:
* solib-svr4.c (struct svr4_info, blah blah other things):
Move earlier.
Tom
next prev parent reply other threads:[~2012-07-19 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 11:05 Gary Benson
2012-07-19 17:02 ` Tom Tromey [this message]
2012-07-19 17:23 ` Gary Benson
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=874np3zntp.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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