From: Teemu Likonen <tlikonen@iki.fi>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation/git-gc.txt: change --aggressive description
Date: Tue, 13 May 2008 14:08:42 +0300 [thread overview]
Message-ID: <20080513110842.GB3088@mithlond.arda.local> (raw)
In-Reply-To: <20080513105728.GA3088@mithlond.arda.local>
Teemu Likonen wrote (2008-05-13 13:57 +0300):
> Pieter de Bie wrote (2008-05-13 11:53 +0200):
>
> > I keep seeing people regularly packing their repo with git gc
> > --aggressive. However, in my experience, this seldom results in
> > a smaller repository. This can be because the repository was
> > repacked tightly previously (for example, with a high --window
> > value) or because incremental "git gc" just makes better packs
> > anyway. Throwing away that information is often not a good idea.
> >
> > The documentation for the --aggressive flag was misleading, in that
> > it hints that you'll get a smaller pack, which is often not the
> > case.
>
> This patch might be a good thing. But from ordinary user's point of
> view this raises questions: if gc --aggressive really is not that
> aggressive then the option itself is misleading. Why not change gc
> --aggressive to be really effective? Using high --window/--depth value
> etc.
I mean, what I'm seeing many places is suggestions to run
git repack -a -d -f --window=100 --depth=100
to get the repo small. _If_ there's such a common need for this then
wouldn't it be good thing if there was easy and self-descriptive command
for it, such as gc --aggressive?
next prev parent reply other threads:[~2008-05-13 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 9:53 [PATCH] Documentation/git-gc.txt: change --aggressive description Pieter de Bie
2008-05-13 10:57 ` Teemu Likonen
2008-05-13 11:08 ` Teemu Likonen [this message]
2008-05-13 11:53 ` Johannes Schindelin
2008-05-13 15:03 ` Teemu Likonen
2008-05-13 11:13 ` Pieter de Bie
2008-05-13 11:52 ` Johannes Schindelin
2008-05-14 6:48 ` Pieter de Bie
2008-05-14 7:48 ` Matthieu Moy
2008-05-24 19:03 ` Pieter de Bie
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=20080513110842.GB3088@mithlond.arda.local \
--to=tlikonen@iki.fi \
--cc=git@vger.kernel.org \
--cc=pdebie@ai.rug.nl \
/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