git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>, git@vger.kernel.org
Subject: Re: Recovering from missing objects?
Date: Fri, 20 Feb 2009 01:10:46 -0500	[thread overview]
Message-ID: <20090220061046.GA28122@coredump.intra.peff.net> (raw)
In-Reply-To: <7vmychiqr3.fsf@gitster.siamese.dyndns.org>

On Thu, Feb 19, 2009 at 10:09:20PM -0800, Junio C Hamano wrote:

> > Might it not be simpler to just copy or hardlink the pack from the new
> > clone into the old directory's .git/objects/pack? That will get more
> > than you need, but things should start working, at which point a "git
> > repack -a -d" will make it small again.
> >
> > Or am I misunderstanding something?
> 
> If you already have a good clone and a half-broken one locally, of course,
> what you said is the easiest.
> 
> I just assumed that Geert did not really want to copy the whole pack.
> Maybe he doesn't mind in this particular case, but the next breakage may
> involve gigapacks he'd rather not re-clone.

Ah, OK. I had the impression that he had already made a new valid clone
on the local box.

> I also assumed that anybody who is reading the message can easily guess
> that the copy I was demonstrating in the description could be done across
> machines, instead of via local /var/tmp/, and "In the new clone" steps
> could even be done in the original one.  Presenting the knowledge that
> way, the solution hopefully would be adjustable for more people who are
> reading this thread.

Makes sense. Thanks.

-Peff

  reply	other threads:[~2009-02-20  6:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 14:08 Recovering from missing objects? Geert Uytterhoeven
2009-02-20  0:29 ` Junio C Hamano
2009-02-20  2:58   ` Jeff King
2009-02-20  6:09     ` Junio C Hamano
2009-02-20  6:10       ` Jeff King [this message]
2009-02-20 14:31   ` Geert Uytterhoeven

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=20090220061046.GA28122@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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;
as well as URLs for NNTP newsgroup(s).