Re: GCC Git mirror no longer updating

From: Eric Wong <normalperson@yhbt.net>
Date: Aug 13, 2009, 03:37 UTC
Message-ID: <20090813033738.GA7950@dcvr.yhbt.net>
In-Reply-To: <1250123299.8074.1593.camel@giskard>

Bernie Innocenti <bernie@codewiz.org> wrote:

Show 16 quoted lines

> El Wed, 12-08-2009 a las 09:45 -0400, Jason Merrill escribió:
> > On 08/12/2009 06:56 AM, Bernie Innocenti wrote:
> > > The git repository format should support concurrent access, but perhaps
> > > it only applies to git-receive-pack, not fancy operations such as
> > > repacking.
> > 
> > The git repository format, yes, but maybe not the stuff in .git/svn.  It 
> > seems like a temporary index file was referring to an object that got 
> > garbage collected away.  Or maybe the index file was left over from the 
> > initial import, and not there due to a collision; there don't seem to be 
> > index files there normally.
> 
> git-svn might be keeping extra information in files that the other git
> tools don't know about.  This would explain why some objects looked
> like orphans and were thus culled.  [cc'ing the git list to catch the
> attention of the git-svn maintainer(s)].

Hi,

As far as I can remember, no version of git svn has ever relied on orphanable objects.

Of course there are unavoidable race conditions that happen while git svn is running. It is never safe to run repack concurrently while git svn is running (I wouldn't repack/gc simultaneously with _any_ write activity on the repo). git svn itself can/will run "git gc" in-between revisions if needed. You can safely repack manually whenever git svn is not running.

-- 
Eric Wong