From: | greg(at)turnstep(dot)com |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] v7.3.1 Bundled and Released ... |
Date: | 2003-01-05 15:10:15 |
Message-ID: | fe4a350269b53ff4158cc720b82a9380@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Well, a tag makes it feasible for someone else to recreate the tarball,
> given access to the CVS server. Dunno how important that is in the real
> world --- but I have seen requests before for us to tag release points.
>
> Any other arguments out there?
FWIW, I use the tags often in some scripts that rely on the output
of 'cvs status -v'. Seeing REL7_3_STABLE at the top of the
"Existing Tags" list is a bit disconcerting when you know that
it's not true. My scripts assume that the latest release should
always be tagged.
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200208
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+GE1NvJuQZxSWSsgRAh/1AKCPEKQeQ3OnKzbeSl5DXstnwwiFPQCfQ2mn
KplkOouzodJqZvQNN2tk8Fk=
=OaZY
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2003-01-06 15:25:47 | GnuPG / PGP signed MD5 checksums for PostgreSQL 7.3.1, 7.3, and 7.2.3 |
Previous Message | Greg Copeland | 2003-01-05 14:53:25 | Re: [GENERAL] v7.3.1 Bundled and Released ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Christian Imbeault | 2003-01-06 02:21:11 | serverlog problems |
Previous Message | Greg Copeland | 2003-01-05 14:53:25 | Re: [GENERAL] v7.3.1 Bundled and Released ... |
From | Date | Subject | |
---|---|---|---|
Next Message | greg | 2003-01-05 15:15:20 | Re: New Portal in Place, DNS switched ... |
Previous Message | Greg Copeland | 2003-01-05 14:53:25 | Re: [GENERAL] v7.3.1 Bundled and Released ... |