From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: jimb@red-bean.com, eliz@gnu.org, gdb-patches@sourceware.org
Subject: Re: [commit] Mention gdb-6.4 release in ChangeLog
Date: Fri, 02 Dec 2005 19:14:00 -0000 [thread overview]
Message-ID: <200512021843.jB2IhfYd004691@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20051202173036.GP1215@adacore.com> (message from Joel Brobecker on Fri, 2 Dec 2005 09:30:36 -0800)
> Date: Fri, 2 Dec 2005 09:30:36 -0800
> From: Joel Brobecker <brobecker@adacore.com>
>
> > 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.
>
> That makes sense to me. If we agree, I can make the adjustment and
> update the documentation.
I like it. I think I'd like to see the "GDB 6.4 branch made" bit also
on the branch, so I suggest to make that change just before branching.
The "Released on 2005-12-02" but can then later be added (and I think
only on the trunk).
Mark
next prev parent reply other threads:[~2005-12-02 18:44 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
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 [this message]
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=200512021843.jB2IhfYd004691@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.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