From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: point git-prune users to git-gc
Date: Tue, 29 Apr 2008 15:05:03 -0700 [thread overview]
Message-ID: <7vskx45ncg.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080429204514.GA21029@sigill.intra.peff.net> (Jeff King's message of "Tue, 29 Apr 2008 16:45:14 -0400")
Jeff King <peff@peff.net> writes:
> Yes, I don't think there is any reason for most people to use git-prune
> at all, unless they are trying specifically to prune and don't want the
> other gc effects to happen.
>
> Junio, please correct me if I'm wrong there.
Well, this is a hard statement to make corrections to. If A is defined to
be a subset of B, and A is generally useful, the only reason to do B is
when you want the effect of B without anything else. So your statement
cannot be incorrect.
However, in order to help people decide when to run B (or, if there ever
be a case where they might want to), there needs a discussion what other
things that _might_ be unwanted A does in addition to B.
For that reason,...
> diff --git a/Documentation/git-prune.txt b/Documentation/git-prune.txt
> index f151cff..f92bb8c 100644
> --- a/Documentation/git-prune.txt
> +++ b/Documentation/git-prune.txt
> @@ -13,6 +13,9 @@ SYNOPSIS
> DESCRIPTION
> -----------
>
> +NOTE: In most cases, users should run linkgit:git-gc[1], which calls
> +git-prune. See the section "NOTES", below.
> +
I think this note upfront is not helping readers very much (this is
git-prune documentation after all -- they are interested in the command
and not gc), but ...
> This runs `git-fsck --unreachable` using all the refs
> available in `$GIT_DIR/refs`, optionally with additional set of
> objects specified on the command line, and prunes all
> @@ -50,6 +53,23 @@ borrows from your repository via its
> $ git prune $(cd ../another && $(git-rev-parse --all))
> ------------
>
> +Notes
> +-----
> +
> +In most cases, users will not need to call git-prune directly, but
> +should instead call linkgit:git-gc[1], which handles pruning along with
> +many other housekeeping tasks.
... this paragraph should be made a bit fatter by mentioning what "other
housekeeping tasks" are.
> +For a description of which objects are considered for pruning, see
> +git-fsck's --unreachable option.
> +
> +See Also
> +--------
> +
> +linkgit:git-fsck[1],
> +linkgit:git-gc[1],
> +linkgit:git-reflog[1]
> +
> Author
> ------
> Written by Linus Torvalds <torvalds@osdl.org>
> --
> 1.5.5.1.172.g4dce
next prev parent reply other threads:[~2008-04-29 22:06 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
2008-04-29 20:45 ` [PATCH] Documentation: point git-prune users to git-gc Jeff King
2008-04-29 22:05 ` Junio C Hamano [this message]
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=7vskx45ncg.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=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).