Re: [SPAM] Re: GIT mirror not updating

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-www(at)postgresql(dot)org, Jeff Davis <pgsql(at)j-davis(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>
Subject: Re: [SPAM] Re: GIT mirror not updating
Date: 2008-12-29 13:25:47
Message-ID: 4958CFDB.3080207@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Heikki Linnakangas wrote:
> Alvaro Herrera wrote:
>> Heikki Linnakangas wrote:
>>
>>> So the procedure is to:
>>>
>>> 1. rsync PostgreSQL main repository.
>>> 2. Remove offending tags:
>>>
>>> cvs -d ~/pgcvsrepository-hacked/ rtag -d REL7_1_BETA2 pgsql
>>> cvs -d ~/pgcvsrepository-hacked/ rtag -d REL7_1_BETA3 pgsql
>>> cvs -d ~/pgcvsrepository-hacked/ rtag -d REL7_1_BETA pgsql
>>
>> Can we permanently hack our repo? It doesn't seem like those tags have
>> a lot of value, after all. (If somebody thinks they do, perhaps we can
>> re-tag.)
>
> I don't know. It's not a big deal, either way.

Or if we can figure out *what* is wrong with them, perhaps we can fix
it? it is some level of historical information that we'd loose, after
all. Granted not very important historical information, but if it's
fixable there's no reason not to do that instead.

//Magnus

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Peter Eisentraut 2008-12-29 14:51:05 Re: [SPAM] Re: GIT mirror not updating
Previous Message Heikki Linnakangas 2008-12-29 13:19:24 Re: [SPAM] Re: GIT mirror not updating