Re: Several tags around PostgreSQL 7.1 broken

*PLEASE* I'll cry again, loudly...

If somebody's doing this type of operation on the CVS replo, please warn
is (I'll consider this warning) *AND STOP RSYNC/ANONCVS ACCESS* around
the operation....

*PLEASE PLEASE PLEASE*

Note that this change doesn't even "fix" the broken CVS history tags;
the REL7_1_BETA[23] tags are the ones that are actually inconsistent.

Note that I'm pausing the CVS->GIT conversion until I hear that the
repository is stable again...

a.

* Peter Eisentraut <peter_e(at)gmx(dot)net> [081229 09:50]:
> I had originally sent this mail in April, but it appears to have been blocked
> because the attachment was too large.
>
> While we are in the process of dealing with CVS-Git conversion, we should also
> apply this fixup to make the CVS repository more sane.
>
> Could someone with write access to the repository files apply this patch?
>
>
> Am Dienstag, 1. April 2008 schrieb Peter Eisentraut:
> > The problem appears to be that several tags around the time of PostgreSQL
> > 7.1 are broken or inconsistent.
>
> Here is a patch to bring the REL7_1 tag in line with the released tarball.
>
> The cvsps errors with the REL7_1_BETA* tags appear to be of a different
> nature. I haven't been able to fix those yet.

>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.