New spin of repository conversion

[Eric S. R. <es...@th...>]

I've pushed a version including the 1.1 release in its tail, and all
previously missing tags should now be visible.

There are somewhere around 275 commits with empty comment fields.
These should either have comments filled in or, if they are ChanegLog
singletons that need to be glued to another clique, I need to know
that.

I've enclosed a file named EMPTY which is in the right format to be
read back in by reposurgeon. All of you, please fill in any comments
you can in the commits you're responsible for; if you want to clue me
in to a ChangeLog commit that should be squashed with the previous
one, put SQUASH in the comment field.  Don't alter the divider lines.

The tags could use some cleanup.

Many of the earlier BETA tags are junk at this point - due to
malformations in the CVS metadata they designate only incomplete sets
of files and don't point at a real (gitspace) commit.  Instead they
point at synthetic commits generated by cvs-fast-export, but what
you'll get if you check out that commit is not reliably what was
originally intended.

I've enclosed a list of these incomplete tags as BADTAGS.  Also
a list of valid tags as GOODTAGS.

My recommended disposition: first, delete all the bad tags.  They're
not actually fit for purpose, and make the repo look like it can restore
state that it can't.

(We may be able to deduce correct replacements for some of the bad tags
by comparing the history with saved release tarballs on SourceForge.)

Second, change all the good release tags to use the same convention.  In
git-land, normal practice is just to use the bare release number as a
release tag. So

GNUPLOT_RELEASE_3_7_1 -> 3.7.1
Release_4_4_2 -> 4.4.3
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.