From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: nickrob@snap.net.nz, gdb-patches@sources.redhat.com
Subject: Re: per-thread variable objects
Date: Wed, 26 Mar 2008 04:32:00 -0000 [thread overview]
Message-ID: <uhceuf6n4.fsf@gnu.org> (raw)
In-Reply-To: <200803250843.25492.vladimir@codesourcery.com> (message from Vladimir Prus on Tue, 25 Mar 2008 08:43:24 +0300)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Tue, 25 Mar 2008 08:43:24 +0300
> Cc: gdb-patches@sources.redhat.com
>
> > > --- gdb/ChangeLog 23 Mar 2008 17:29:32 -0000 1.9247
> > > +++ gdb/ChangeLog 24 Mar 2008 17:31:09 -0000
> > > @@ -1,3 +1,15 @@
> > >...
> >
> > I think ChangeLog entries shouldn't be presented as diffs.
>
> Does that cause any practical issue to anybody?
Not a big deal, but it is indeed customary to send ChangeLog entries
themselves, not as diffs.
next prev parent reply other threads:[~2008-03-26 4:32 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 [this message]
2008-03-26 12:06 ` Daniel Jacobowitz
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=uhceuf6n4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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