From: Jim Blandy <jimb@red-bean.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, eliz@gnu.org, gdb-patches@sourceware.org
Subject: Re: [commit] Mention gdb-6.4 release in ChangeLog
Date: Sat, 03 Dec 2005 04:20:00 -0000 [thread overview]
Message-ID: <8f2776cb0512021428j17f2f169h23433cc4b2a2101b@mail.gmail.com> (raw)
In-Reply-To: <200512021843.jB2IhfYd004691@elgar.sibelius.xs4all.nl>
On 12/2/05, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> 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).
It would be nice to have the branchpoint indicated on the branch, too.
But people do want to know release dates when looking on the branch,
too.
The specific maneuver you're suggesting, however, is impossible if
you're doing a "post facto" branch, using -D; I know Andrew did this a
few times, and I thought Joel was going to, too. Post-facto branching
uses a non-HEAD revision as the branch point, so you'd have to modify
history in order to get the ChangeLog entry in there before you
branched.
The hair here is the result of having two distinct "histories": the
ChangeLog, and CVS.
next prev parent reply other threads:[~2005-12-02 22:28 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
2005-12-03 4:20 ` Jim Blandy [this message]
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=8f2776cb0512021428j17f2f169h23433cc4b2a2101b@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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