From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: -stack-list-frames HIGH_FRAME changes
Date: Fri, 05 May 2006 19:20:00 -0000 [thread overview]
Message-ID: <vt2ac9wp9ca.fsf@theseus.home.> (raw)
In-Reply-To: <20060505145349.GB28855@nevyn.them.org> (Daniel Jacobowitz's message of "Fri, 5 May 2006 10:53:49 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Fri, May 05, 2006 at 06:38:19PM +0400, Vladimir Prus wrote:
>> The reason I've included them in patch is that I've learned about Emacs's
>> add-change-log-entry command, which conveniently adds entry to existing
>> file ;-) So, in case if there are several ChangeLog files in patch, I should
>> put those entries separately, and indicate which file each entry goes to,
>> right?
>
> Right. I usually don't bother when it's obvious (e.g. there's only one
> file named gdb.texinfo, and it's obviously in gdb/doc/).
>
> Alexandre Oliva wrote a script to pull the entries out of diffs
> automatically, if you prefer.
If you use Emacs, I have a patch-cleanup command that:
- pulls out ChangeLog patches
- removes patches to generated files *if* there is also a patch to
the presumed source file (so Makefile.in patches get removed if
there is an accompanying Makefile.am patch, but not otherwise).
Let me know if you're interested.
next prev parent reply other threads:[~2006-05-05 19:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 7:54 Vladimir Prus
2006-05-05 10:30 ` Eli Zaretskii
2006-05-05 13:51 ` Daniel Jacobowitz
2006-05-05 14:39 ` Vladimir Prus
2006-05-05 14:53 ` Daniel Jacobowitz
2006-05-05 19:20 ` Jim Blandy [this message]
2006-05-05 15:46 ` Bob Rossi
2006-05-05 14:52 ` Daniel Jacobowitz
2006-09-07 16:10 ` Daniel Jacobowitz
2006-09-07 16:41 ` Vladimir Prus
2006-05-05 21:13 ` Eli Zaretskii
2006-09-07 16:10 ` Vladimir Prus
2006-09-07 22:37 Nick Roberts
2006-09-07 23:10 ` Daniel Jacobowitz
2006-09-08 6:28 ` Vladimir Prus
2006-09-08 8:30 ` Nick Roberts
2006-09-08 8:39 ` Vladimir Prus
2006-09-08 14:33 ` Daniel Jacobowitz
2006-09-08 16:37 ` Eli Zaretskii
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=vt2ac9wp9ca.fsf@theseus.home. \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sources.redhat.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