git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Question about git-prune

From
Wwalt <wa1ter@myrealbox.com>
Date
Jun 30, 2007, 20:06 UTC
Message-ID
<f66d3l$sa6$1@sea.gmane.org>
In-Reply-To
<Pine.LNX.4.64.0706301900290.4438@racer.site>
Johannes Schindelin wrote:
> Hi,
> 
> On Sat, 30 Jun 2007, walt wrote:
...
Show 8 quoted lines
>> $git-prune
>> $git-fsck
>> dangling tree c642c018aa55d39fff061183f58062de9d8375ac
>> dangling commit e1341abc3759950e891822088cb0163b71b316b3
>> dangling commit 9f38e1ef7e7992ca490b9b419f52fb4d11efb0e4
>> dangling commit b82871b3c32faa8a317007f343fdf2d0ddc9954e
> 
> Probably the objects were packed.
I also tried git-prune-packed, which also did nothing AFAICT.
> I do not understand why you use git-prune directly, to begin with. Why not 
> use git-gc and be done with it?

It didn't exist when I started using git. I normally don't use git-prune either, but in this case I was just scanning for problems after switching from cg-update to git-pull.

git-gc did get rid of all the danglers even though git-prune didn't. I'll do some investigating to find out why -- that should get me more up to date with recent changes.

Thanks for your help.
Previous: Johannes SchindelinNext: Junio C Hamano
Message 3 of 5 in “Question about git-prune”
  1. waltJun 30, 2007
  2. Johannes SchindelinJun 30, 2007
  3. waltJun 30, 2007
  4. Junio C HamanoJun 30, 2007
  5. Johannes SchindelinJun 30, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.