LKML Archive on
help / color / mirror / Atom feed
From: Junio C Hamano <>
To: Jeff Garzik <>
Subject: Re: [ANNOUNCE] GIT
Date: Sun, 09 Mar 2008 23:34:22 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Jeff Garzik <> writes:

> Yes, I regularly run both 'git gc' and 'git prune'.
> But since (ref original email) I was doing some rebasing, there are
> inevitably changesets left dangling after such an operation.

Yeah, I'd say it is stupid if "am" ran "gc --auto" for every patch.  I
recall that we had the same issue with git-svn and we made it run once
every 1k round, and we probably should do the same for "am" and "rebase",
running once at the very end.

I notice however that git-am does exactly that.  It runs "gc --auto" only
at the end, and does not run it when it stops upon unapplicable patch.

Perhaps we would want to raise the default "gc --auto" limit?  Currently
when it estimates that you have roughly 6700 objects unpacked it runs
"repack --prune-packed", and if there still are that many unpacked objects
after that, it suggests you to run "git prune" to remove them.  If you are
rebasing, the commits in the old history that are rewritten will _not_
immediately become dangling because they will still be reachable from your
reflog.  If you are getting the message, these objects were already
dangling (ancient commits that are not even reachable from your reflog
entries that are by default kept for 90 days) even before you started your
rebase or am run.

After you finished your day's work on a typical day, what does the output
from "git count-objects -v" and "git fsck-objects" look like, I wonder?

  reply	other threads:[~2008-03-10  6:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 21:07 [ANNOUNCE] GIT Junio C Hamano
2008-03-09 10:46 ` [ANNOUNCE] GIT Junio C Hamano
2008-03-09 16:56   ` Jeff Garzik
2008-03-09 20:28     ` Junio C Hamano
2008-03-09 21:42       ` Jeff Garzik
2008-03-10  6:34         ` Junio C Hamano [this message]
2008-03-11 19:11           ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] GIT' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).