All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Guimmara" <sebastien.guimmara@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v9 2/5] command-list.txt: add the common groups block
Date: Wed, 20 May 2015 21:51:33 +0200	[thread overview]
Message-ID: <555CE5C5.8000209@gmail.com> (raw)
In-Reply-To: <CAPig+cTM4L7Vt1gYb5zvAgt8hsqGQdLWigN_yB-VsWukNbt=zw@mail.gmail.com>



On 05/20/2015 09:48 PM, Eric Sunshine wrote:
> On Wed, May 20, 2015 at 3:22 PM, Sébastien Guimmara
> <sebastien.guimmara@gmail.com> wrote:
>> The ultimate goal is for "git help" to display common commands in
>> groups rather than alphabetically. As a first step, define the
>> groups in a new block, and then assign a group to each
>> common command.
>>
>> Add a block at the beginning of command-list.txt:
>>
>>      init         start a working area (see also: git help tutorial)
>>      worktree     work on the current change (see also:[...]
>>      info         examine the history and state (see also: git [...]
>>      history      grow, mark and tweak your history
>>      remote       collaborate (see also: git help workflows)
>>
>> storing information about common commands group, then map each common
>> command to a group:
>>
>>      git-add          mainporcelain        common worktree
>>
>> Signed-off-by: Sébastien Guimmara <sebastien.guimmara@gmail.com>
>> ---
>>   command-list.txt | 50 ++++++++++++++++++++++++++++++--------------------
>>   1 file changed, 30 insertions(+), 20 deletions(-)
>
> Hmm, did your update to Documentation/technical/new-command.txt get
> lost? I don't see it any of the patches, but would have expected it to
> be included in this patch which introduces the "common groups"
> section.
>

Ah, you're right. A commit got lost in the process. Will fix that. Thanks.

>> diff --git a/command-list.txt b/command-list.txt
>> index 609b344..c2bbdc1 100644
>> --- a/command-list.txt
>> +++ b/command-list.txt
>> @@ -1,3 +1,13 @@
>> +# common commands are grouped by themes output by 'git help'
>> +# map each common command in the command list to one of these groups.
>
> Discussed previously: It also would be a good idea to mention that the
> order in which "git help" displays the groups themselves is the order
> they are declared here. Maybe just add one more line between the two
> you already have above:
>
>      # groups are output by 'git help' in the order declared here.
>

Indeed, I'll add the mention.

>> +### common groups
>
> In the block below, the "### command list" line is protected by a "#
> do not molest the next line" warning. Perhaps the same should be done
> here? Alternately, make them more compact by incorporating the
> warning:
>
>      ### common groups (do not change this line)
>      ...
>      ### command list (do not change this line)
>
> ?
>

Yes, it's better. I shall modify this.

>> +init         start a working area (see also: git help tutorial)
>> +worktree     work on the current change (see also: git help everyday)
>> +info         examine the history and state (see also: git help revisions)
>> +history      grow, mark and tweak your common history
>> +remote       collaborate (see also: git help workflows)
>> +
>> +# List of known git commands.
>>   # do not molest the next line
>>   ### command list
>>   # command name                          category [deprecated] [common]

  reply	other threads:[~2015-05-20 19:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 19:22 [PATCH v9 0/5] group common commands by theme Sébastien Guimmara
2015-05-20 19:22 ` [PATCH v9 1/5] command-list: prepare machinery for upcoming "common groups" section Sébastien Guimmara
2015-05-20 19:22 ` [PATCH v9 2/5] command-list.txt: add the common groups block Sébastien Guimmara
2015-05-20 19:48   ` Eric Sunshine
2015-05-20 19:51     ` Sébastien Guimmara [this message]
2015-05-20 19:22 ` [PATCH v9 3/5] generate-cmdlist: parse common group commands Sébastien Guimmara
2015-05-20 19:27   ` Sébastien Guimmara
2015-05-20 19:32     ` Stefan Beller
2015-05-20 19:34       ` Sébastien Guimmara
2015-05-20 19:32     ` Eric Sunshine
2015-05-20 19:23 ` [PATCH v9 4/5] command-list.txt: drop the "common" tag Sébastien Guimmara
2015-05-20 19:23 ` [PATCH v9 5/5] help: respect new common command grouping Sébastien Guimmara
2015-05-20 21:39   ` Ramsay Jones
2015-05-20 21:42     ` Sébastien Guimmara
2015-05-20 19:31 ` [PATCH v9 0/5] group common commands by theme Eric Sunshine

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=555CE5C5.8000209@gmail.com \
    --to=sebastien.guimmara@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.