-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --On Tuesday, April 01, 2008 14:06:09 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
>> In the meantime, does anyone have more information about how this came about?
>
> Marc's always done both the tagging and the tarball-making, so you'd
> have to ask him about that. I believe he's made it more scripted over
> the years, so this might reflect a manual foulup that (hopefully) is no
> longer possible.
Ya, I'll go with that (considering 7.1 was back in 2001 ... ) ... but, from the
way Peter describes it (taging partially checked out code), I'm not 100% how
its possible to 'foul up' ... a tag operation is:
cvs -q update -APd .
cvs -q tag REL7_1 .
unless its a sub-tagging, which would have:
cvs -q update -rREL7_1_STABLE -Pd .
cvs -q tag REL7_1_1 .
And since I don't do the update until things are "quiet" (generally when Tom
has finished his last commit before release), I'm not sure how I could have
gotten a 'partial checkout' ...
> +1 for adjusting the tags in CVS to match what we actually shipped.
Agreed ... but, stupid question here ... if our tags are wrong in CVS, are the
7.1.x releases themselves wrong too? When I do a release tarball, I run:
cvs -q export -rREL7_1_1 pgsql
so, if the tags are wrong, then all of those releases are wrong too, since they
are based on the tag ...
- --
Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFH8tX24QvfyHIvDvMRAndoAJ9KA86BZl21zLb3rie9ynlmDL7BHQCfdtjB
VrYLsml4H+ppnXvC26ywKTU=
=RWHE
-----END PGP SIGNATURE-----
