applying gpg-signed tags for previous releases

[Jim Meyering]

FYI, there was only one public/annotated tag for sed's
releases.  That made it harder than necessary to
determine for what release a given change was made.
To remedy that situation, I have done the following:

Apply a signed tag corresponding to the version
increment in configure.ac for each new release.
Back-date each tag so that it has the same
date as the corresponding commit.

for h in \
 $(git log --pretty=oneline|grep -E 'bump version( number)?'|sed 's/ .*//'); \
  date=$(git log --pretty=%ci -1 $h)
  v=$(git show $h|perl -lne '/^\+AC_INIT\(.*?, (.*?),/ and print $1')
  v=v$v
  GIT_COMMITTER_DATE="$date" git tag -s -m$v $v $h
done

# And then I pushed with git push --tags origin

Here are the hash/tag pairs from the above:

e265d716a9d72027a97dde96d1234c2210e28a6b
v4.2.2
feaa20792f8c65d4c8de669a6770ebc3d5973d1e
v4.2.1
5a30fa2129f6d9e7d96362c6929ae006896cda1c
v4.2
4381be08bd6b4acf9ff808018fc197c12cb26ef7
v4.1f
068afd076e5b48599772616ddd4a3496ac6778ba
v4.1c
f6aa842534f3435a2150f7bd1968e83dee1872b8
v4.1b
44536f208ae55319a34773d9d117f0b3c9f859e3
v4.1.5
-----------------------------
That did the above, but left holes, e.g.,
for 4.1a, 4.1d and 4.1e.  I manually identified
those (albeit only looking at when the version
number changed in configure.ac, and not comparing
with actual tarballs) and applied with this:

for h in \
  c1067081c5fbfd98b3660370887666df18243587 \
  cba6413f07c39d757bafcfff411588e3c0631627 \
  6ea4dbce16b6c4cc0d9bfd0e81adec62aa87a7e7 \
; do
  date=$(git log --pretty=%ci -1 $h)
  v=$(git show $h|perl -lne '/^\+AC_INIT\(.*?, (.*?),/ and print $1')
  v=v$v
  echo $date: $v
  GIT_COMMITTER_DATE="$date" git tag -s -m$v $v $h
done