From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: per-thread variable objects
Date: Wed, 26 Mar 2008 12:06:00 -0000 [thread overview]
Message-ID: <20080326120614.GA11331@caradoc.them.org> (raw)
In-Reply-To: <uhceuf6n4.fsf@gnu.org>
On Wed, Mar 26, 2008 at 06:31:27AM +0200, Eli Zaretskii wrote:
> Not a big deal, but it is indeed customary to send ChangeLog entries
> themselves, not as diffs.
For instance, if I need to grab the patch from the mailing list
archives to backport it to an older version of GDB - I do that often.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-26 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 17:46 Vladimir Prus
2008-03-24 21:00 ` Nick Roberts
2008-03-25 5:44 ` Vladimir Prus
2008-03-26 4:32 ` Eli Zaretskii
2008-03-26 12:06 ` Daniel Jacobowitz [this message]
2008-04-01 14:13 ` Daniel Jacobowitz
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=20080326120614.GA11331@caradoc.them.org \
--to=drow@false.org \
--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