GNU Binutils 2.41 release

[Nick Clifton]

Hi H.J.

> The binutils-2_41 tag points to the wrong commit:
> 
> d3cc73ee4a (HEAD -> binutils-2_41-branch, origin/binutils-2_41-branch)
> Updated Spanish translation for the gprof directory
> ae85bd64903 Automatic date update in version.in
> 7872e3bdb0d Reset 2.41 branch back to development mode
> 2c73aeb8d2e (tag: binutils-2_41) The 2.41 release!
> 
> The binutils-2_41 tag has
> 
> m4_define([BFD_VERSION], [2.40.90])

Darn.  I am not sure that I can do anything about this.

I must have missed running "git commit; git push" after changing
bfd/version.m4 to:

   m4_define([BFD_VERSION], [2.41])

And then making the source release tarballs.  So the tarballs are
OK but the tag points to an earlier version of the sources, just
before the release happened.  The problem is, there is no commit
that exactly corresponds to the released sources, so I cannot create
a new tag for the release point.

Any ideas ?

Cheers
   Nick

PS.  I have updated the README-how-to-make-a-release file to add
   a note to check for pending commits just before creating the source
   tarballs, so hopefully this issue will not happen again in the
   future.