From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-gc doesn't clean up leftover objects after git-filter-branch unless you clone first
Date: Thu, 24 Apr 2008 12:59:34 -0400 [thread overview]
Message-ID: <32541b130804240959y3b05d4b5u67ac7a7c14bf187e@mail.gmail.com> (raw)
In-Reply-To: <20080424161407.GA23737@sigill.intra.peff.net>
On 4/24/08, Jeff King <peff@peff.net> wrote:
> Hmm, maybe it would make sense to put that note in git-prune, with a
> note in git-gc to look at the prune page.
Perhaps.
> But if the note were moved to git-prune, it would be natural to mention
> git-reflog there. What do you think?
I gather there's a movement in recent git versions (sorry, I only
tuned in recently) to encourage people to use git-gc instead of
git-prune in almost all cases. The reasons I ever looked at git-prune
at all was that git-gc mentioned it in "See Also", and because
"git-prune" sounded more obviously like what I wanted than "git-gc"
when I looked at "man git".
Adding git-gc *and* git-reflog as See Also entries in git-prune would
make sense to me.
Avery
next prev parent reply other threads:[~2008-04-24 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 15:41 git-gc doesn't clean up leftover objects after git-filter-branch unless you clone first Avery Pennarun
2008-04-23 17:00 ` Junio C Hamano
2008-04-23 18:36 ` Avery Pennarun
2008-04-23 22:13 ` Jeff King
2008-04-24 1:28 ` Jeff King
2008-04-24 15:43 ` Avery Pennarun
2008-04-24 16:14 ` Jeff King
2008-04-24 16:59 ` Avery Pennarun [this message]
2008-04-29 20:45 ` [PATCH] Documentation: point git-prune users to git-gc Jeff King
2008-04-29 22:05 ` Junio C Hamano
2008-04-29 23:19 ` Jeff King
2008-04-30 1:01 ` Junio C Hamano
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=32541b130804240959y3b05d4b5u67ac7a7c14bf187e@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).