From: Andreas Ericsson <ae@op5.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jari Aalto <jari.aalto@cante.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add commands that git-gc runs underneath
Date: Thu, 30 Aug 2007 14:13:18 +0200 [thread overview]
Message-ID: <46D6B45E.4020800@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0708301254420.28586@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> On Thu, 30 Aug 2007, Andreas Ericsson wrote:
>
>> I kinda like it [listing the commands git-gc calls], and it might be
>> helpful if someone's got a large repo and one part of gc for some reason
>> didn't complete so they want to start at whatever step it broke off on.
>
> Let me clarify: I do not like the listing in the man page. This suggests
> to the user to delve into plumbing areas where it is all too easy to shoot
> yourself in the foot.
>
I misunderstood.
> I have nothing against listing the commands per se. But the man page is
> too exposed IMHO. (Or would you like to add the original shell script to
> git-log's man page, too?)
>
> My preferred location would be somewhere near Documentation/technical/, so
> that people reading the commands are more likely to understand the
> consequences.
>
> But maybe I'm wrong.
>
Having read the reasoning, I confess myself convinced. Thanks for clarifying.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-08-30 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 9:35 [PATCH] Add commands that git-gc runs underneath Jari Aalto
2007-08-30 10:08 ` Johannes Schindelin
2007-08-30 10:13 ` Andreas Ericsson
2007-08-30 11:58 ` Johannes Schindelin
2007-08-30 12:13 ` Andreas Ericsson [this message]
2007-08-30 12:15 ` Tom Clarke
2007-08-30 12:34 ` Theodore Tso
2007-08-30 21:33 ` Junio C Hamano
2007-08-31 9:33 ` Andreas Ericsson
2007-08-31 19:25 ` David Kastrup
2007-08-31 21:12 ` Junio C Hamano
2007-08-31 21:27 ` David Kastrup
2007-08-30 10:25 ` David Kastrup
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=46D6B45E.4020800@op5.se \
--to=ae@op5.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.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