From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v2] test-lib: limit the output of the yes utility
Date: Wed, 3 Feb 2016 13:11:57 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1602031309550.2964@virtualbox> (raw)
In-Reply-To: <56B0F259.1060100@kdbg.org>
Hi Hannes,
On Tue, 2 Feb 2016, Johannes Sixt wrote:
> I'm not 100% satisfied with your version because it stomps on
> short-and-sweet shell variables $i and $y.
Please note that $y was already stomped on before my patch.
> But then the utility only occurs upstream of a pipeline in a separate
> process, so that does not matter.
That was my thinking, too.
> Please allow me to pass authorship to you, since the patch text is
> now all yours, and to forge your sign-off.
Fair enough,
Dscho
prev parent reply other threads:[~2016-02-03 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 7:28 [PATCH] test-lib: limit the output of the yes utility Johannes Sixt
2016-02-02 8:21 ` Johannes Schindelin
2016-02-02 18:15 ` [PATCH v2] " Johannes Sixt
2016-02-03 12:11 ` Johannes Schindelin [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=alpine.DEB.2.20.1602031309550.2964@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/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).