From: Jim Blandy <jimb@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Mention gdb-6.4 release in ChangeLog
Date: Fri, 02 Dec 2005 17:35:00 -0000 [thread overview]
Message-ID: <8f2776cb0512020927p2652a411v7c4aa8bf3815914f@mail.gmail.com> (raw)
In-Reply-To: <uiru7blv6.fsf@gnu.org>
On 12/2/05, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 2 Dec 2005 08:54:37 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > On Thu, Dec 01, 2005 at 11:36:38PM -0800, Joel Brobecker wrote:
> > > I added the following entry at the top of the ChangeLog in the head
> > > branch:
> > >
> > > 2005-12-02 Joel Brobecker <brobecker@adacore.com>
> > >
> > > GDB 6.4 released from GDB 6.4 branch.
> > >
> > > This shows when the release was made.
> >
> > Is this useful?
>
> I think it is. Sometimes, one needs to know when a particular version
> was released.
People working quickly will definitely assume that whatever entry they
come across first marks the branchpoint.
I think we should have a single ChangeLog entry at the branchpoint,
and include the release date in that ChangeLog entry:
2005-11-21 Joel Brobecker <...>
* GDB 6.4 branch made. Released on 2005-12-02.
next prev parent reply other threads:[~2005-12-02 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 7:40 Joel Brobecker
2005-12-02 14:38 ` Daniel Jacobowitz
2005-12-02 14:43 ` Daniel Jacobowitz
2005-12-02 17:27 ` Eli Zaretskii
2005-12-02 17:35 ` Jim Blandy [this message]
2005-12-02 17:47 ` Joel Brobecker
2005-12-02 17:56 ` Kevin Buettner
2005-12-02 18:38 ` Daniel Jacobowitz
2005-12-02 19:14 ` Mark Kettenis
2005-12-03 4:20 ` Jim Blandy
2005-12-02 18:49 ` 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=8f2776cb0512020927p2652a411v7c4aa8bf3815914f@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=eliz@gnu.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