git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: "Sébastien Guimmara" <sebastien.guimmara@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v11 0/5] group common commands by theme
Date: Thu, 21 May 2015 14:15:05 -0400	[thread overview]
Message-ID: <CAPig+cQtYjyj2dVFX_8CjyacRPd+dU6aMMXYGsoX9+q+zgjdZQ@mail.gmail.com> (raw)
In-Reply-To: <1432229962-21405-1-git-send-email-sebastien.guimmara@gmail.com>

On Thu, May 21, 2015 at 1:39 PM, Sébastien Guimmara
<sebastien.guimmara@gmail.com> wrote:
> Just a minor change, the modification of new-command.txt was squashed to
> 2/5 instead of 1/5.

Thanks. With or without addressing the two very minor nits I pointed
out in patches 2/5 and 5/5, this entire patch series (v11) is:

Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>

> Eric Sunshine (2):
>   command-list: prepare machinery for upcoming "common groups" section
>   generate-cmdlist: parse common group commands
>
> Sébastien Guimmara (3):
>   command-list.txt: add the common groups block
>   command-list.txt: drop the "common" tag
>   help: respect new common command grouping
>
>  Documentation/cmd-list.perl         |  4 +++
>  Documentation/howto/new-command.txt |  4 ++-
>  Makefile                            |  9 ++++---
>  command-list.txt                    | 53 ++++++++++++++++++++++---------------
>  generate-cmdlist.perl               | 50 ++++++++++++++++++++++++++++++++++
>  generate-cmdlist.sh                 | 23 ----------------
>  help.c                              | 24 ++++++++++++++++-
>  7 files changed, 117 insertions(+), 50 deletions(-)
>  create mode 100755 generate-cmdlist.perl
>  delete mode 100755 generate-cmdlist.sh

      parent reply	other threads:[~2015-05-21 18:15 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
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 ` Eric Sunshine [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPig+cQtYjyj2dVFX_8CjyacRPd+dU6aMMXYGsoX9+q+zgjdZQ@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sebastien.guimmara@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).