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 18:01:52 -0700 [thread overview]
Message-ID: <7v63u040lb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080429231917.GB22646@sigill.intra.peff.net> (Jeff King's message of "Tue, 29 Apr 2008 19:19:17 -0400")
Jeff King <peff@peff.net> writes:
> I'm not so sure that they are interested in the prune command. At first
> I started with just a note near the end, but the point of this is
> specifically to deal with users who "stumble" upon prune, either from
> reading the command list (i.e., trying to match a command to the
> objective they want to perform) or from pre-gc tutorials or emails which
> mention it.
Ah, you are right. People tend to stop reading when they _think_ they
heard enough even though they haven't. The note upfront is good, and I
suspect we would not have to reword the latter parts either then.
>> > +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.
>
> OK, I was trying to imply "go look at git-gc for those tasks" so they
> didn't have to be repeated. Would you prefer it be spelled out
> explicitly here, or is a more firm pointer OK?
Will apply as is.
Thanks.
prev parent reply other threads:[~2008-04-30 1:02 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
2008-04-29 23:19 ` Jeff King
2008-04-30 1:01 ` Junio C Hamano [this message]
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=7v63u040lb.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).