This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: gdb-7.9-release tag on wrong commit
- From: Pedro Alves <palves at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>, Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 19 Feb 2015 12:56:16 +0000
- Subject: Re: RFC: gdb-7.9-release tag on wrong commit
- Authentication-results: sourceware.org; auth=none
- References: <1424347460-31023-1-git-send-email-brobecker at adacore dot com> <20150219122319 dot GF23529 at adacore dot com> <20150219124010 dot GG23529 at adacore dot com> <8338623w96 dot fsf at gnu dot org>
On 02/19/2015 12:45 PM, Eli Zaretskii wrote:
>> 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.
Agreed.
To minimize confusion, you can also delete the bad tag, and
then most people won't ever see it. Those who managed to
pull in the bad tag in can get rid of it with
e.g., "git pull --prune --tags".
Thanks,
Pedro Alves