All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Steven Grimm <koreth@midwinter.com>,
	Brian Gernhardt <benji@silverinsanity.com>
Subject: Re: [PATCH 2/2] Documentation/git-gc: improve description of --auto
Date: Thu, 18 Oct 2007 22:29:09 -0400	[thread overview]
Message-ID: <20071019022909.GZ14735@spearce.org> (raw)
In-Reply-To: <20071019020510.GB7711@coredump.intra.peff.net>

Jeff King <peff@peff.net> wrote:
> It is a little bit odd that there is so much low-level detail in the
> '--auto' description versus the rest of the page. But I think it reads
> OK. Also note that the previous incarnation (and my changes) use the
> `foo` form to monospace arguments, while the rest of the page uses 'foo'
> (which actually means emphasis). I think the former is more correct, but
> asciidoc renders the latter much more pleasantly in manpages. I will see
> if I can tweak asciidoc to make this look better.

I like this a lot better than what was there before.  Nice work.
I have no real opinion on the asciidoc syntax.

I personally prefer to read commands in the source as `foo` and
feel that asciidoc should just format it correctly for the backend.
If it isn't then we should try to work with the asciidoc folks to
get it right...

>  --auto::
> -	With this option, `git gc` checks if there are too many
> -	loose objects in the repository and runs
> -	gitlink:git-repack[1] with `-d -l` option to pack them.
> -	The threshold for loose objects is set with `gc.auto` configuration
> -	variable, and can be disabled by setting it to 0.  Some
> -	Porcelain commands use this after they perform operation
> -	that could create many loose objects automatically.
> -	Additionally, when there are too many packs are present,
> -	they are consolidated into one larger pack by running
> -	the `git-repack` command with `-A` option.  The
> -	threshold for number of packs is set with
> -	`gc.autopacklimit` configuration variable.
> +	With this option, `git gc` checks whether any housekeeping is
> +	required; if not, it exits without performing any work.
> +	Some git commands run `git gc --auto` after performing
> +	operations that could create many loose objects.
> ++
> +Housekeeping is required if there are too many loose objects or
> +too many packs in the repository. If the number of loose objects
> +exceeds the value of the `gc.auto` configuration variable, then
> +all loose objects are combined into a single pack using
> +`git-repack -d -l`.  Setting the value of `gc.auto` to 0
> +disables automatic packing of loose objects.
> ++
> +If the number of packs exceeds the value of `gc.autopacklimit`,
> +then existing packs (except those marked with a `.keep` file)
> +are consolidated into a single pack by using the `-A` option of
> +`git-repack`. Setting `gc.autopacklimit` to 0 disables
> +automatic consolidation of packs.

-- 
Shawn.

  reply	other threads:[~2007-10-19  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  2:05 [PATCH 2/2] Documentation/git-gc: improve description of --auto Jeff King
2007-10-19  2:29 ` Shawn O. Pearce [this message]
2007-10-19  2:38   ` Jeff King
2007-10-19  4:45     ` Jeff King

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=20071019022909.GZ14735@spearce.org \
    --to=spearce@spearce.org \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    --cc=koreth@midwinter.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.