Re: [SPAM] Re: GIT mirror not updating

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-www(at)postgresql(dot)org
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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 14:51:05
Message-ID: 200812291651.06429.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Monday 29 December 2008 15:25:47 Magnus Hagander wrote:
> 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.

I analyzed this back in April; my analysis is in the archives. The short
version is that it is probably a bug in cvsps.

See also my message to hackers just now about a repository fixup that we *can*
do.

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Chander Ganesan 2008-12-29 15:00:29 Consistent company naming in training list..
Previous Message Magnus Hagander 2008-12-29 13:25:47 Re: [SPAM] Re: GIT mirror not updating