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

Re: dangling commits

From
MRMarco Roeland <marco.roeland@xs4all.nl>
Date
Jan 16, 2006, 08:52 UTC
Message-ID
<20060116085238.GA3768@fiberbit.xs4all.nl>
In-Reply-To
<20060115221108.3ED2E352659@atlas.denx.de>
On Sunday January 15th 2006 Wolfgang Denk wrote:
> Is ther eany way to clean up such a situation and really get  rid  of
> the  dangling  commits?  I understand that I'd first need some way to
> "unpack" the packs, but how to do this?

Note that apart from the disk space they use up, dangling commits don't do any harm.

However you can easily get rid of them by using "git prune".

As far as I know although packs are used in transferring the commits to your local repository they are stored there as separate objects, so you certainly don't have to unpack things yourself for using "git prune". Git is quite smart, fast and safe on its own I find each time! It really is a wonderful tool by giving you every possibility to work with it without inflicting policy on you.

If wanted you can use "git repack -a -d" followed by "git prune-packed" to create a tight packed repository (all commits and blobs in one pack) but there is no specific need to.

-- 
Marco Roeland
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 15 in “dangling commits”
  1. Nick WilliamsJan 15, 2006
  2. Andreas EricssonJan 15, 2006
  3. Nick WilliamsJan 15, 2006
  4. Junio C HamanoJan 15, 2006
  5. Wolfgang DenkJan 15, 2006
  6. Junio C HamanoJan 15, 2006
  7. Marco RoelandJan 16, 2006
  8. Junio C HamanoJan 16, 2006
  9. Marco RoelandJan 16, 2006
  10. Andreas EricssonJan 16, 2006
  11. Marco RoelandJan 16, 2006
  12. Andreas EricssonJan 16, 2006
  13. Marco RoelandJan 16, 2006
  14. Wolfgang DenkJan 16, 2006
  15. Marco RoelandJan 16, 2006

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.