From: Junio C Hamano <gitster@pobox.com>
To: "Sébastien Guimmara" <sebastien.guimmara@gmail.com>
Cc: git@vger.kernel.org, sunshine@sunshineco.com
Subject: Re: [PATCH 0/5] git help: group common commands by theme
Date: Thu, 14 May 2015 13:51:44 -0700 [thread overview]
Message-ID: <xmqqa8x6khlr.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1431608351-9413-1-git-send-email-sebastien.guimmara@gmail.com> ("Sébastien Guimmara"'s message of "Thu, 14 May 2015 14:59:05 +0200")
Sébastien Guimmara <sebastien.guimmara@gmail.com> writes:
> This v6 is very similar in content to the v5 [1], except minor formatting
> adjustments in 'git help' output and recommendations from Eric.
>
> The major change is in the patch series itself. Commits have been
> reordered and adjusted so that each 'apply' doesn't break the build, and
> preserve bisectability.
Hmph, did you decide to abandon the "whitespace fix" patch? This
does not seem to be based on that one, and it would be crazy to
have these patches *and* the other one as independent two topics
and expect them to be merged cleanly later.
next prev parent reply other threads:[~2015-05-14 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 12:59 [PATCH 0/5] git help: group common commands by theme Sébastien Guimmara
2015-05-14 12:59 ` [PATCH 1/5] command-list.txt: prepare with [commands] header Sébastien Guimmara
2015-05-14 12:59 ` [PATCH 2/5] command-list.txt: add with [common] block Sébastien Guimmara
2015-05-14 12:59 ` [PATCH 3/5] generate-cmdlist: parse common group commands Sébastien Guimmara
2015-05-14 20:58 ` Junio C Hamano
2015-05-14 21:05 ` Eric Sunshine
2015-05-15 14:40 ` Sébastien Guimmara
2015-05-14 12:59 ` [PATCH 4/5] command-list.txt: drop the common- prefix Sébastien Guimmara
2015-05-14 12:59 ` [PATCH 5/5] help.c: output the typical Git workflow Sébastien Guimmara
2015-05-14 12:59 ` Sébastien Guimmara
2015-05-14 20:51 ` Junio C Hamano [this message]
2015-05-15 14:37 ` [PATCH 0/5] git help: group common commands by theme Sébastien Guimmara
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=xmqqa8x6khlr.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sebastien.guimmara@gmail.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.