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

Re: Cleaning the .git directory with gc

From
Russ Dill <russ.dill@gmail.com>
Date
Apr 24, 2008, 00:09 UTC
Message-ID
<f9d2a5e10804231709v1d7e426fwf68b3d316a15081a@mail.gmail.com>
In-Reply-To
<20080423231359.GA30913@fox>
On Wed, Apr 23, 2008 at 4:13 PM, Haakon Riiser <haakon.riiser@fys.uio.no> wrote:
> I've recently started using git, and while experimenting with
>  git commit --amend, I noticed that git gc does not do what I
>  expected.  Example:
Thats a lot of work without first reading the man page:
       --prune
           Usually git-gc packs refs, expires old reflog entries, packs loose
           objects, and removes old rerere records. Removal of unreferenced
           loose objects is an unsafe operation while other git operations are
           in progress, so it is not done by default. Pass this option if you
           want it, and only when you know nobody else is creating new objects
           in the repository at the same time (e.g. never use this option in a
           cron script).
Previous: Haakon RiiserNext: David Tweed
Message 2 of 6 in “Cleaning the .git directory with gc”
  1. Haakon RiiserApr 23, 2008
  2. Russ DillApr 24, 2008
  3. David TweedApr 24, 2008
  4. Shawn O. PearceApr 24, 2008
  5. Shawn O. PearceApr 24, 2008
  6. Haakon RiiserApr 24, 2008

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.