Git development
 help / color / mirror / Atom feed
From: Bernie Innocenti <bernie@codewiz.org>
To: Jason Merrill <jason@redhat.com>
Cc: Daniel Berlin <dberlin@dberlin.org>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	overseers@gcc.gnu.org, git@vger.kernel.org
Subject: Re: GCC Git mirror no longer updating
Date: Thu, 13 Aug 2009 02:28:19 +0200	[thread overview]
Message-ID: <1250123299.8074.1593.camel@giskard> (raw)
In-Reply-To: <4A82C786.5060602@redhat.com>

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)].

Ah, and I just fixed a problem I have introduced myself while fiddling
to recover the repository: HEAD should point at "refs/remotes/trunk",
otherwise new commits won't show up in gitweb.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

       reply	other threads:[~2009-08-13  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A8198E2.5020205@redhat.com>
     [not found] ` <1250008005.8074.362.camel@giskard>
     [not found]   ` <20090811163049.GA4578@redhat.com>
     [not found]     ` <1250010535.8074.366.camel@giskard>
     [not found]       ` <20090811173006.GB4578@redhat.com>
     [not found]         ` <1250017013.8074.376.camel@giskard>
     [not found]           ` <20090811191642.GA5806@redhat.com>
     [not found]             ` <4aca3dc20908111333i49195ec5h9b91ab5f6445f701@mail.gmail.com>
     [not found]               ` <4A822440.40207@redhat.com>
     [not found]                 ` <1250074569.8074.671.camel@giskard>
     [not found]                   ` <4A82C786.5060602@redhat.com>
2009-08-13  0:28                     ` Bernie Innocenti [this message]
2009-08-13  3:37                       ` GCC Git mirror no longer updating Eric Wong
     [not found]                         ` <4aca3dc20908130743g28a32229s194e9caa7a44fa2@mail.gmail.com>
2009-08-13 21:51                           ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1250123299.8074.1593.camel@giskard \
    --to=bernie@codewiz.org \
    --cc=dberlin@dberlin.org \
    --cc=fche@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=jason@redhat.com \
    --cc=overseers@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox