From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Update README post gdb-6.5 branch creation
Date: Wed, 17 May 2006 03:39:00 -0000 [thread overview]
Message-ID: <ulkt12uco.fsf@gnu.org> (raw)
In-Reply-To: <20060516200632.GR4123@adacore.com> (message from Joel Brobecker on Tue, 16 May 2006 13:06:32 -0700)
> Date: Tue, 16 May 2006 13:06:32 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> The version number currently used is gdb-6.3. In the 6.5 branch, I think
> it makes sense to have it use gdb-6.5. But in the head, I think it makes
> sense to use gdb-6.6. That way, assuming we follow the usual pattern of
> only increasing the minor version number for the next release, I don't
> have to update this file at all after I cut the gdb-6.6 branch.
I think README in the CVS head should say 6.5.50.cvs or some such, so
that people who build snapshots would see the right version.
If we accept Daniel's proposal, this will happen automatically.
prev parent reply other threads:[~2006-05-17 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 20:09 Joel Brobecker
2006-05-16 20:12 ` Daniel Jacobowitz
2006-05-16 20:22 ` Joel Brobecker
2006-05-17 4:36 ` Eli Zaretskii
2006-05-17 3:39 ` Eli Zaretskii [this message]
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=ulkt12uco.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.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