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 v11 2/5] command-list.txt: add the common groups block
Date: Mon, 25 May 2015 19:31:48 +0200 [thread overview]
Message-ID: <55635C84.7080108@gmail.com> (raw)
In-Reply-To: <CAPig+cRciCgBZyuT4fz0JZLY9SRmODaXq=gvsimVQ7sdt+AzcA@mail.gmail.com>
On 05/21/2015 08:01 PM, Eric Sunshine wrote:
> On Thu, May 21, 2015 at 1:39 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.
>>
>> Helped-by: Eric Sunshine <sunshine@sunshineco.com>
>> Helped-by: Junio C Hamano <gitster@pobox.com>
>> Helped-by: Emma Jane Hogbin Westby <emma.westby@gmail.com>
>> Signed-off-by: Sébastien Guimmara <sebastien.guimmara@gmail.com>
>> ---
>> diff --git a/command-list.txt b/command-list.txt
>> index 181a9c2..32ddab3 100644
>> --- a/command-list.txt
>> +++ b/command-list.txt
>> @@ -1,3 +1,14 @@
>> +# common commands are grouped by themes
>> +# these groups are output by 'git help' in the order declared here.
>> +# map each common command in the command list to one of these groups.
>> +### common groups (do not change this line)
>> +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.
>
> This is odd. The above line was removed in 1/5 but then re-appears
> here in 2/5. I think the intent is that it should remain removed.
>
>> ### command list (do not change this line)
>> # command name category [deprecated] [common]
>> git-add mainporcelain common
My mistake. This will be corrected in the next version. Thank you for taking time
to review this series.
Sébastien
next prev parent reply other threads:[~2015-05-25 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 17:39 [PATCH v11 0/5] group common commands by theme Sébastien Guimmara
2015-05-21 17:39 ` [PATCH v11 1/5] command-list: prepare machinery for upcoming "common groups" section Sébastien Guimmara
2015-05-21 17:39 ` [PATCH v11 2/5] command-list.txt: add the common groups block Sébastien Guimmara
2015-05-21 18:01 ` Eric Sunshine
2015-05-25 17:31 ` Sébastien Guimmara [this message]
2015-05-26 18:31 ` Eric Sunshine
2015-05-26 19:13 ` Junio C Hamano
2015-05-21 17:39 ` [PATCH v11 3/5] generate-cmdlist: parse common group commands Sébastien Guimmara
2015-05-21 17:39 ` [PATCH v11 4/5] command-list.txt: drop the "common" tag Sébastien Guimmara
2015-05-21 17:39 ` [PATCH v11 5/5] help: respect new common command grouping Sébastien Guimmara
2015-05-21 18:04 ` Eric Sunshine
2015-05-25 17:25 ` Sébastien Guimmara
2015-05-21 18:15 ` [PATCH v11 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=55635C84.7080108@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.