git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>, Duy Nguyen <pclouds@gmail.com>,
	Antoine Pelisse <apelisse@gmail.com>
Subject: Re: [PATCH v2 1/4] builtin: add git-check-mailmap command
Date: Thu, 11 Jul 2013 23:34:46 -0700	[thread overview]
Message-ID: <7vmwpsnv5l.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAPig+cTwXe7rSKUgJPVHbAvrxYbmL77xNXtLyUeRnd8Taxtrdw@mail.gmail.com> (Eric Sunshine's message of "Fri, 12 Jul 2013 02:24:43 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

>> I find it easier than your original, but I do not know if you would
>> want to repeat the "Name... or <user@host>" at the end.  It does not
>> seem to add much useful information and is distracting.
>
> Next attempt:
>
>     For each ``Name $$<user@host>$$'' or ``$$<user@host>$$'' from the
>     command-line or standard input (when using `--stdin`) look up the
>     person's canonical name and email address (see "Mapping Authors"
>     below). If found, print them; otherwise print the input as-is.

Nice.

> ... Is it desirable to do so
> or should the user have more fine-grained control? ("xargs -0" comes
> to mind when thinking of a null-termination input switch.)

For the purposes of check-attr and check-ignore, a single "-z"
governing both is sufficient.  I think you already got that from my
4-patch series, but the core reason for that is :

 - when "-z" is used, the user knows the input paths may need
   protection against LF.

 - our output contains these same paths.

 - which means our output cannot be expressed unambiguously using LF
   as record separator.

For the purpose of check-mailmap, I actually do not see much point
in supporting "-z" format.  We do not even handle names or addresses
with LF in it.  The mailmap format would not let you express such
records in the first place, no?

  reply	other threads:[~2013-07-12  6:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 14:55 [PATCH v2 0/4] add git-check-mailmap command Eric Sunshine
2013-07-11 14:55 ` [PATCH v2 1/4] builtin: " Eric Sunshine
2013-07-11 19:04   ` Junio C Hamano
2013-07-12  3:28     ` Eric Sunshine
2013-07-12  5:47       ` Junio C Hamano
2013-07-12  6:24         ` Eric Sunshine
2013-07-12  6:34           ` Junio C Hamano [this message]
2013-07-12  6:39             ` Eric Sunshine
2013-07-11 14:55 ` [PATCH v2 2/4] t4203: test check-mailmap command invocation Eric Sunshine
2013-07-11 14:55 ` [PATCH v2 3/4] t4203: test mailmap functionality directly rather than indirectly Eric Sunshine
2013-07-11 19:07   ` Junio C Hamano
2013-07-12  0:35     ` Eric Sunshine
2013-07-12  0:55       ` Jonathan Nieder
2013-07-12  2:37         ` Eric Sunshine
2013-07-12  5:48         ` Junio C Hamano
2013-07-12  6:05           ` Eric Sunshine
2013-07-12  6:25             ` Junio C Hamano
2013-07-11 14:55 ` [PATCH v2 4/4] t4203: consolidate test-repository setup 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=7vmwpsnv5l.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=apelisse@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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 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).