From: Jeff Garzik <jgarzik@pobox.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-prune-script eats data
Date: Tue, 21 Jun 2005 20:51:53 -0400 [thread overview]
Message-ID: <42B8B629.1040208@pobox.com> (raw)
Ok, I have a reproducible case (at least for me), of git-prune-script
munching data. I'll just give reproduction instructions (everyone
reading this can do what I did), and some output at the end.
$ cd /repos
$ mkdir libata-dev-test/.git
$ cd libata-dev-test
$ cp -al ../linux-2.6/.git/objects .git/
$ rsync -az --verbose --delete \
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git/
.git/ # word-wrapped from previous line
$ git-checkout-script -f
$ git-fsck-cache
dangling commit 1b142a71f3b131317489edf806abfab4c347476c
dangling commit 51a7f407d9b600e3278449a12135a21ffb0791a2
dangling commit eb93f3e7284204379444137a660b64f9dbd2ec04
dangling commit fcf604172829176bc618663e8387c8943ff88b66
NOTE: These dangling commits are NORMAL -- stuff that really does need
pruning.
$ git-prune-script
$ git-fsck-cache
error: cannot map sha1 file c39ae07f393806ccf406ef966e9a15afc43cc36a
bad object in tag 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c
bad sha1 entry '5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c'
$ rsync -az --verbose --delete \
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git/
.git/ # word-wrapped from previous line
# this second invocation downloads a TON of objects,
# most/all of which are in the vanilla linux-2.6 tree
# and should not have been pruned
next reply other threads:[~2005-06-22 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 0:51 Jeff Garzik [this message]
2005-06-23 2:04 ` git-prune-script eats data Linus Torvalds
2005-06-23 5:25 ` Jeff Garzik
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=42B8B629.1040208@pobox.com \
--to=jgarzik@pobox.com \
--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.