From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-www@postgresql.org
Subject: Re: GIT repo broken
Date: Wed, 2 Jul 2008 14:18:28 +0200
User-Agent: KMail/1.9.9
Cc: "Greg Sabino Mullane" <greg@turnstep.com>
References: <03e9397c93dbb9654bdbb5ea804b52ec@biglumber.com>
In-Reply-To: <03e9397c93dbb9654bdbb5ea804b52ec@biglumber.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200807021418.29207.peter_e@gmx.net>

Am Montag, 30. Juni 2008 schrieb Greg Sabino Mullane:
> The cvs->git import script doesn't handle branches yet: this is a known
> problem, just wanted to reply here so there it is on record. No idea of
> when it might be fixed: I looked it over, but I need stronger git/ruby
> skills and/or more free time to figure it all out.

I think the tool does handle branches, it just broke somewhere along the way 
and now it doesn't continue.  It has been suspected that this happens when 
the git-cvs update happens while an rsync of the CVS repository is in 
progress, owing to the nonatomic nature of CVS.

We should probably rebuild the Git repository sometime, but everytime you do 
that all the commit IDs change, and I haven't had the enthusiasm yet to give 
users a proper recipe for dealing with that, e.g., pulling and merging or 
rebasing to adjust existing clones to the upstream.  If someone has an idea 
how to deal with the latter, I'd appreciate that.