From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: gdb-7.9-release tag on wrong commit (was: "Re: [release/branch] Set GDB version number to str 7.9.")
Date: Thu, 19 Feb 2015 12:45:00 -0000 [thread overview]
Message-ID: <8338623w96.fsf@gnu.org> (raw)
In-Reply-To: <20150219124010.GG23529@adacore.com>
> Date: Thu, 19 Feb 2015 16:40:10 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> I'm not sure what to do:
> 1. Create a new tag (Eg: "gdb-7.9.0-release")
> 2. Just re-do the tag (aka "the insane way")
> 3. Leave things as is
> 4. Abandon "7.9" and release "7.9.1" instead...
>
> I am leaning towards option 4...
Wouldn't it be even more confusing to have 7.9.1 without 7.9?
I'd say creating a new tag is good enough.
next prev parent reply other threads:[~2015-02-19 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 12:04 [release/branch] Set GDB version number to str 7.9 Joel Brobecker
2015-02-19 12:23 ` Joel Brobecker
2015-02-19 12:40 ` RFC: gdb-7.9-release tag on wrong commit (was: "Re: [release/branch] Set GDB version number to str 7.9.") Joel Brobecker
2015-02-19 12:45 ` Eli Zaretskii [this message]
2015-02-19 12:57 ` RFC: gdb-7.9-release tag on wrong commit Pedro Alves
2015-02-19 13:46 ` Joel Brobecker
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=8338623w96.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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