git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: Scott Chacon <schacon@gmail.com>, git list <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] Group the default git help message by topic
Date: Fri, 11 Jun 2010 18:00:47 -0400	[thread overview]
Message-ID: <4C12B20F.3080709@gmail.com> (raw)
In-Reply-To: <422F3619-25EC-4509-8EE3-78B6C765AB2A@wincent.com>

Wincent Colaiuta wrote:
> El 11/06/2010, a las 18:03, Scott Chacon escribió:
> 
>> +	puts("The most commonly used git commands are:\n");
>> +
>> +	puts("Basic Commands:");
>> +	print_command("init");
>> +	print_command("clone");
>> +	print_command("add");
>> +	print_command("status");
>> +	print_command("commit");
>> +	puts("");
>> +
>> +	puts("Branch Commands:");
>> +	print_command("branch");
>> +	print_command("checkout");
>> +	print_command("merge");
>> +	print_command("tag");
>> +	puts("");
>> +
>> +	puts("History Commands:");
>> +	print_command("log");
>> +	print_command("diff");
>> +	print_command("reset");
>> +	print_command("show");
>> +	puts("");
>> +
>> +	puts("Remote Commands:");
>> +	print_command("remote");
>> +	print_command("fetch");
>> +	print_command("pull");
>> +	print_command("push");
> 
> Nice. I'm sure the output will be a bit less intimidating, but I am not sure about some of the grouping choices you've made here.
> 
> "git checkout" is almost certainly a "Basic" command, even though it's used for creating and switching branches.
> 
> "git tag" doesn't really seem to be a "Branch" command, as it's for tagging objects (usually commits), and not branches.
> 
> "git reset" is the odd one out in the "History" commands group. The other three commands are about _inspecting_ history, whereas "git reset" is about changing the current HEAD. I actually think "git reset" fits better with the "Branch" commands.
> 
> I think I'd be inclined to use more descriptive headings and group the commands like this:
> 
>   Basic operation:
>     init
>     add
>     status
>     commit
>     checkout
> 
>   Inspecting repository state and history:
>     log
>     diff
>     show
> 
>   Working with branches:
>     branch
>     merge
>     reset
> 
>   Interacting with other repositories:
>     clone
>     fetch
>     pull
>     push
>     remote
> 
> ...</end of my 2 cents>

Can a command be listed twice? Some of these commands _really_ belong in 
more than one category.

  reply	other threads:[~2010-06-11 22:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 16:03 [PATCH v2] Group the default git help message by topic Scott Chacon
2010-06-11 16:26 ` Wincent Colaiuta
2010-06-11 22:00   ` A Large Angry SCM [this message]
2010-06-11 22:28     ` Ævar Arnfjörð Bjarmason
2010-06-12 16:19       ` Scott Chacon
2010-06-12 16:35         ` Ævar Arnfjörð Bjarmason
2010-06-12 18:44       ` A Large Angry SCM
2010-06-12 16:17   ` Scott Chacon
2010-06-12 17:53     ` Wincent Colaiuta
2010-06-11 16:46 ` Ævar Arnfjörð Bjarmason
2010-06-14  6:30 ` Junio C Hamano
2010-06-14 15:31   ` Scott Chacon
2010-06-14 16:49     ` Tay Ray Chuan
2010-06-14 16:59       ` Scott Chacon
2010-06-14 17:24     ` Junio C Hamano
2010-06-14  7:48 ` Matthieu Moy

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=4C12B20F.3080709@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=schacon@gmail.com \
    --cc=win@wincent.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).