All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: git@vger.kernel.org
Subject: How to fetch missing pack
Date: Sat, 12 Apr 2008 12:07:12 +0000 (UTC)	[thread overview]
Message-ID: <slrng019fg.nd8.joerg@alea.gnuu.de> (raw)

Hi,

I'm missing a pack. My history of the git repository is broken:
% git show --pretty=raw e0fda6ab|head -7
commit e0fda6abd11c567b72f29ec0ee06c541404a9cb7
tree 77a7e4a849bbec646d88ae863f80ea3f519e26bd
parent 1ab58e8d6f728cdde0057f7ee88daab3a1c2d06f
author Wincent Colaiuta <win@wincent.com> 1196066088 +0100
committer Junio C Hamano <gitster@pobox.com> 1196109124 -0800

    Fix typo in draft 1.5.4 release notes
% git log --pretty=oneline e0fda6ab | wc -l
1
% git show e0fda6ab~1|cat
fatal: ambiguous argument 'e0fda6ab~1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

Can I somehow tell git fetch to check the whole history for holes and
fetch missing packs?

Bye, Jörg.
-- 
Der kommt den Göttern am nächsten, der auch dann schweigen kann,
wenn er im Recht ist.                         (Cato; 234–149 v. Chr.)

             reply	other threads:[~2008-04-12 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 12:07 Jörg Sommer [this message]
2008-04-13  9:41 ` How to fetch missing pack Peter Baumann
2008-04-23 20:55   ` Jörg Sommer
2008-04-24  6:01     ` Christian Couder
2008-04-24  6:08       ` Shawn O. Pearce
2008-04-27 10:47         ` git doesn't finds the parent of a commit (was: How to fetch missing pack) Jörg Sommer
2008-04-27 17:37           ` Stephen R. van den Berg
2008-04-27 20:18             ` git doesn't finds the parent of a commit Junio C Hamano
2008-04-27 21:46               ` Stephen R. van den Berg
2008-04-28 14:14             ` Jörg Sommer

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=slrng019fg.nd8.joerg@alea.gnuu.de \
    --to=joerg@alea.gnuu.de \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.