From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Sébastien Guimmara" <sebastien.guimmara@gmail.com>,
"Git List" <git@vger.kernel.org>
Subject: Re: [PATCH v8 5/5] help: respect new common command grouping
Date: Tue, 19 May 2015 12:35:58 -0400 [thread overview]
Message-ID: <CAPig+cS15yzwbcdb-yLH5QiMoxa0utmaJaDDz=W9WfWd+PL37A@mail.gmail.com> (raw)
In-Reply-To: <xmqq1tica6rk.fsf@gitster.dls.corp.google.com>
On Tue, May 19, 2015 at 12:09 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Eric Sunshine <sunshine@sunshineco.com> writes:
>
>> The awk script restricts itself to POSIX, and I did test it on Linux,
>> Mac OS X, and FreeBSD, so it seems pretty portable.
>
> I was worried more about some people only having gawk while others
> with mawk and yet others nawk, etc., without having one of them
> under the canonical name "awk". It's nothing what
>
> $ make AWK=mawk
>
> or its config.mak equivalent cannot fix, but still bothers me a bit.
In that case, perhaps we should go with the Perl version, which, given
that more people (these days) are familiar with Perl than awk, is less
likely to be a maintenance burden.
next prev parent reply other threads:[~2015-05-19 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 19:18 [PATCH v8 0/5] group common commands by theme Sébastien Guimmara
2015-05-18 19:18 ` [PATCH v8 1/5] command-list: prepare machinery for upcoming "common groups" section Sébastien Guimmara
2015-05-18 19:18 ` [PATCH v8 2/5] command-list.txt: add the common groups block Sébastien Guimmara
2015-05-18 19:18 ` [PATCH v8 3/5] generate-cmdlist: parse common group commands Sébastien Guimmara
2015-05-18 19:18 ` [PATCH v8 4/5] command-list.txt: drop the "common" tag Sébastien Guimmara
2015-05-18 19:18 ` [PATCH v8 5/5] help: respect new common command grouping Sébastien Guimmara
2015-05-18 21:39 ` Junio C Hamano
2015-05-19 0:43 ` Eric Sunshine
2015-05-19 16:09 ` Junio C Hamano
2015-05-19 16:35 ` Eric Sunshine [this message]
2015-05-19 18:20 ` Junio C Hamano
2015-05-19 17:57 ` 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='CAPig+cS15yzwbcdb-yLH5QiMoxa0utmaJaDDz=W9WfWd+PL37A@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.
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).