RFC: gdb-7.9-release tag on wrong commit (was: "Re: [release/branch] Set GDB version number to str 7.9.")

[Joel Brobecker <brobecker@adacore.com>]

On Thu, Feb 19, 2015 at 04:23:19PM +0400, Joel Brobecker wrote:
> > In preparation for the GDB 7.9 release, I am about to push
> > this commit...
> > 
> > gdb/ChangeLog:
> > 
> > 	* version.in: Set GDB version number to str 7.9.
> [...]
> > diff --git a/gdb/version.in b/gdb/version.in
> > index 8c98182..2d982e4 100644
> > --- a/gdb/version.in
> > +++ b/gdb/version.in
> > @@ -1 +1 @@
> > -7.8.90.DATE-cvs
> > +str 7.9
> 
> For those who were actually paying attention (not me), there is
> an obvious mistake in the version number.
[...]
> But I was sleeping at the wheel. Fortunately, I caught it slightly
> later on. Attached is the patch that fixes the issue.

Humpf, I am realizing now that this was not soon enough:
I already pushed the gdb-7.9-release tag, and that tag
points to the first commit, and therefore has the wrong
version number in it.

The normal thing to do in those cases is to just accept the mistake
and create a new tag, tagging the correct commit. I find it so very
very ugly, but if I were to fix the tag, anyone having pulled from
sourceware would already have the "wrong" one, and would later on
have to delete the tag from their repository before they can get
the new one.

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...

Thoughts?
-- 
Joel