From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Scott Chacon <schacon@gmail.com>, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Modified the default git help message to be grouped by topic
Date: Mon, 01 Dec 2008 17:45:12 -0800 [thread overview]
Message-ID: <7v7i6jqriv.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081201183258.GB24443@coredump.intra.peff.net> (Jeff King's message of "Mon, 1 Dec 2008 13:32:59 -0500")
Jeff King <peff@peff.net> writes:
> On Mon, Dec 01, 2008 at 09:30:37AM -0800, Scott Chacon wrote:
>
>> It's difficult to process 21 commands (which is what is output
>> by default for git when no command is given). I've re-grouped
>> them into 4 groups of 5 or 6 commands each, which I think is
>> clearer and easier for new users to process.
>
> I like it (and I think the categorizations look reasonable, which is
> something that I recall caused some discussion at the GitTogether).
>
> The only downside I see is that we're now >24 lines.
If this list is meant to show "the most commonly used" basics, then you
can trim the list somewhat. For example, "rm" and "mv" can be safely
discarded, "status" can be replaced with "diff", and "diff" can be removed
from "History Commands".
next prev parent reply other threads:[~2008-12-02 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 17:30 [PATCH] Modified the default git help message to be grouped by topic Scott Chacon
2008-12-01 18:32 ` Jeff King
2008-12-02 1:45 ` Junio C Hamano [this message]
2008-12-02 6:10 ` Scott Chacon
2008-12-02 20:11 ` James Pickens
2008-12-02 21:33 ` Boyd Stephen Smith Jr.
2008-12-02 22:55 ` Johannes Schindelin
2008-12-02 23:30 ` Jeff King
2008-12-02 23:39 ` Scott Chacon
2008-12-03 0:10 ` Junio C Hamano
2008-12-03 0:37 ` Jeff King
2008-12-03 0:47 ` Jakub Narebski
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=7v7i6jqriv.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=schacon@gmail.com \
/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).