From: Junio C Hamano <gitster@pobox.com>
To: "Øystein Walle" <oystwa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v7 00/11] Add interpret-trailers builtin
Date: Mon, 10 Mar 2014 08:27:02 -0700 [thread overview]
Message-ID: <xmqqa9cyrs55.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <loom.20140308T124447-78@post.gmane.org> ("Øystein Walle"'s message of "Sat, 8 Mar 2014 11:54:14 +0000 (UTC)")
Øystein Walle <oystwa@gmail.com> writes:
> Junio C Hamano <gitster <at> pobox.com> writes:
>
>>
>> ...
>>
>> is easier to read and maintain if written like so (with using HT
>> properly---our MUAs may damage it and turn the indentation into
>> spaces):
>>
>> ... &&
>> sed -e "s/ Z$/ /" >>expect <<-\EOF &&
>> Fixes: Z
>> Acked-by= Z
>> Reviewed-by: Z
>> Signed-off-by: Z
>> EOF
>> ...
>>
>
> How about:
>
> printf '%s: \n' Fixes Acked-by Reviewed-by Signed-off-by >> expect
Not really.
> This solution scores high marks in both readability and maintainability
> in my mind.
I actually considered that approach while I was writing the message
you responded to, but discarded it because it forces us to commit to
the view that we forsee no need to test an output that does not end
with a trailing whitespace. And I do not think that is a limitation
we want to place on this test.
prev parent reply other threads:[~2014-03-10 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 22:06 [PATCH v7 00/11] Add interpret-trailers builtin Christian Couder
2014-03-07 21:49 ` Junio C Hamano
2014-03-08 11:54 ` Øystein Walle
2014-03-10 15:27 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa9cyrs55.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=oystwa@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 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.