-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- --On Wednesday, April 02, 2008 17:49:49 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: > It doesn't, of course. What it does do is guarantee that the tarball > matches the tag that has already been laid down in CVS. 'k, that was my thought, so using export vs update to create the tarbal is irrelevant to this discussion ... > But there must have been more to it than that. Peter is reporting > that the tag is on mutually inconsistent versions of some files; > which means that the problem was with the tagging operation more than > with the tarball-making. Has anyone actually checked the tarballs themselves? If the tag's are wrong, then doesn't it follow that the tarballs themselves are all wrong too? - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH9BQr4QvfyHIvDvMRAjC9AJ9qBRom7aU7LWmZGnhfOFtbwv7zRQCgxPqx qv5B4ffClv4RRXc2FVg6LpI= =zjTy -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
