To: Aidan Van Dyk <aidan@highrise.ca>
cc: Andrew Dunstan <andrew@dunslane.net>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up 
In-reply-to: <20090526144812.GC15213@yugib.highrise.ca> 
References: <937d27e10904270840vaf70c0fr37518478b31d8a15@mail.gmail.com>
	<4A189843.3010200@agliodbs.com>
	<20090524165012.GL8123@tamriel.snowman.net>
	<4A1A52F5.7030009@hagander.net>
	<20090525122821.GO8123@tamriel.snowman.net>
	<4A1BABBC.7070803@hagander.net> <4A1BE039.70008@dunslane.net>
	<10273.1243343651@sss.pgh.pa.us> <4A1BFF70.4000506@dunslane.net>
	<20090526144812.GC15213@yugib.highrise.ca>
Comments: In-reply-to Aidan Van Dyk <aidan@highrise.ca>
	message dated "Tue, 26 May 2009 10:48:12 -0400"
Date: Tue, 26 May 2009 11:19:42 -0400
Message-ID: <12570.1243351182@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Aidan Van Dyk <aidan@highrise.ca> writes:
> This has been raised and ignored many times before on -hackers... The
> reason is because the tags in the CVS repository are "broken" (i.e they
> are such that it's impossible to actually create all the tags), so the
> git "cvsimport" tools that try to tags all croak on the PG CVS repository.

> The tool which doesn't croak doesn't try and import all the tags, just
> the sticky "branch tags"...

> Scripts to "fix" (actually, remove) the broken tags have also been
> posted, along with requests that if somebody is "mucking" with the
> actual repository, to make sure it's known about, and access is "denied"
> during the mucking period (access being any rsync/anoncvs/mirroring of
> the cvs root).

Up to now I've always been of the opinion that fixing those tags wasn't
worth taking any risk for.  But if we are thinking of moving away from
CVS, then this clearly becomes one of the hurdles we have to jump on the
way.  Can you refresh our memory about which tags are problematic and
exactly what needs to be done about 'em?

			regards, tom lane