Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.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: Tue, 16 May 2006 20:12:00 -0000	[thread overview]
Message-ID: <20060516201144.GA12800@nevyn.them.org> (raw)
In-Reply-To: <20060516200632.GR4123@adacore.com>

On Tue, May 16, 2006 at 01:06:32PM -0700, Joel Brobecker wrote:
> Hello,
> 
> Now that the gdb-6.5 branch has been created, one the items that needs
> to be done is the update of the README file. Normally, it just consists
> of bumping the version number up, but in this case, I have a question.
> 
> 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 therefore propose the following patch for the head:
> 
> 2006-05-16  Joel Brobecker  <brobecker@adacore.com>
> 
>         * README: Update GDB version number.
> 
> What do you guys think?

For at least the last couple of releases, this file has just gotten
sedded.  Should we have a README.in instead?  It would still need to be
proofread at some point on the release checklist - but GCC has adopted
a strict "version number in one place only" policy and it seems to be
quite helpful.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-16 20:11 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 [this message]
2006-05-16 20:22   ` Joel Brobecker
2006-05-17  4:36   ` Eli Zaretskii
2006-05-17  3:39 ` 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=20060516201144.GA12800@nevyn.them.org \
    --to=drow@false.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