All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.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 11:20:03 -0700	[thread overview]
Message-ID: <xmqq617o8m5o.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAPig+cS15yzwbcdb-yLH5QiMoxa0utmaJaDDz=W9WfWd+PL37A@mail.gmail.com> (Eric Sunshine's message of "Tue, 19 May 2015 12:35:58 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> 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.

As long as we all can agree that the long-term direction we want to
go in is to remove dependency on awk, that's fine by me.

That means a small awk scriptlets in t/ and elsewhere need to be
rethought, though.

Thanks.

  reply	other threads:[~2015-05-19 18:20 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
2015-05-19 18:20           ` Junio C Hamano [this message]
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=xmqq617o8m5o.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.