From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-gc.txt: change --aggressive description
Date: Tue, 13 May 2008 12:52:01 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0805131251320.30431@racer> (raw)
In-Reply-To: <1210672413-8761-1-git-send-email-pdebie@ai.rug.nl>
Hi,
On Tue, 13 May 2008, Pieter de Bie wrote:
> The documentation for the --aggressive flag was misleading, hinting that
> running git gc with --aggressive is a good thing. However, --aggressive
> only really makes sense if you have a bad pack file, such as from
> git-fast-import.
I disagree. It makes sense to "git gc --aggressive" also after cloning
from somebody who did not do so.
Ciao,
Dscho
next prev parent reply other threads:[~2008-05-13 11:52 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
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 [this message]
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=alpine.DEB.1.00.0805131251320.30431@racer \
--to=johannes.schindelin@gmx.de \
--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