From: Marc G. Fournier <scrappy@hub.org>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Tue, 26 May 2009 18:54:52 -0300 (ADT)
Message-ID: <20090526185313.T35116@hub.org> (raw)
In-Reply-To: <20090526153501.GG15213@yugib.highrise.ca>
References: <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>
<12570.1243351182@sss.pgh.pa.us>
<20090526153501.GG15213@yugib.highrise.ca>
On Tue, 26 May 2009, Aidan Van Dyk wrote:
> * Tom Lane <tgl@sss.pgh.pa.us> [090526 11:20]:
>> 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?
>
> Specifically, it's 2 tags, and I just remove them:
> REL7_1_BETA2
> REL7_1_BETA3
So, you are suggesting:
cvs -q tag -d REL7_1_BETA2 .
cvs -q tag -d REL7_1_BETA3 .
correct?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: scrappy@hub.org, aidan@highrise.ca, tgl@sss.pgh.pa.us, andrew@dunslane.net
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <20090526185313.T35116@hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox