From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: Question about git-prune
Date: Sat, 30 Jun 2007 09:29:04 -0700 [thread overview]
Message-ID: <Pine.LNX.4.64.0706300915440.16800@x2.ybpnyarg> (raw)
I'm wondering why git-prune seems to work differently on the two git
repositories I track (Junio's and Linus's).
Specifically, when I use git-prune on Linus's kernel, all the dangling
objects disappear completely, and git-fsck shows no objects remaining.
But this is what happens with Junio's repository:
$cd src/git
$git-fsck
dangling tree c642c018aa55d39fff061183f58062de9d8375ac
dangling commit e1341abc3759950e891822088cb0163b71b316b3
dangling commit 9f38e1ef7e7992ca490b9b419f52fb4d11efb0e4
dangling commit b82871b3c32faa8a317007f343fdf2d0ddc9954e
$git-prune
$git-fsck
dangling tree c642c018aa55d39fff061183f58062de9d8375ac
dangling commit e1341abc3759950e891822088cb0163b71b316b3
dangling commit 9f38e1ef7e7992ca490b9b419f52fb4d11efb0e4
dangling commit b82871b3c32faa8a317007f343fdf2d0ddc9954e
And here is another puzzle:
$git-fsck --unreachable
unreachable commit f291504563a5c96862e600247d233f91572a005f
unreachable tree 0e925e128b7b83750e2b8b0d901d7d518cadbdaf
unreachable tree c642c018aa55d39fff061183f58062de9d8375ac
unreachable tree 0b43ac348827a25d54a6fc90c36c12c4c6bdd6c1
unreachable tree 4d43b9900856904cdfc69769124b1930435dae51
unreachable commit e1341abc3759950e891822088cb0163b71b316b3
unreachable blob 590533321a99bf4d00b872a839527f00616ed593
unreachable tree e355b3845361c5f0c829bd146c47c77867aa36a3
unreachable tree 7e08ac7c56e51ea94db1dd6525c26fe123537b07
unreachable commit 9f38e1ef7e7992ca490b9b419f52fb4d11efb0e4
unreachable commit b82871b3c32faa8a317007f343fdf2d0ddc9954e
unreachable commit 750f7b668f33c9e8decbdd8141115328992d6fea
git-prune is supposed to remove all the unreachable objects, IIUC,
so it seems that git-prune does nothing at all in Junio's repo.
Can anyone reproduce this behavior, or explain it?
Thanks.
next reply other threads:[~2007-06-30 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 16:29 walt [this message]
2007-06-30 18:02 ` Question about git-prune Johannes Schindelin
2007-06-30 20:06 ` walt
2007-06-30 20:12 ` Junio C Hamano
2007-06-30 20:18 ` Johannes Schindelin
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=Pine.LNX.4.64.0706300915440.16800@x2.ybpnyarg \
--to=wa1ter@myrealbox.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 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).