From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Eric Sunshine" <sunshine@sunshineco.com>,
"Git List" <git@vger.kernel.org>,
"Michael Blume" <blume.mike@gmail.com>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH] t0060: loosen overly strict expectations
Date: Fri, 15 Jan 2016 09:26:14 -0800 [thread overview]
Message-ID: <xmqq60yukb49.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1601150734460.2964@virtualbox> (Johannes Schindelin's message of "Fri, 15 Jan 2016 07:35:34 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> > This is not limited to the "//" vs "/" case, of course, other inputs are
>> > also allowed to produce multiple outpus by the POSIX specs.
>>
>> s/outpus/outputs/
>
> Whoops.
>
> Junio, would you terribly mind adjusting the commit message on your end?
No problem. Is this the only tweak that is necessary before it can
go to 'next' and then to 'master'?
next prev parent reply other threads:[~2016-01-15 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 6:48 [PATCH] t0060: loosen overly strict expectations Johannes Schindelin
2016-01-14 17:33 ` Junio C Hamano
2016-01-14 18:13 ` Ramsay Jones
2016-01-14 22:14 ` Johannes Sixt
2016-01-15 0:46 ` Ramsay Jones
2016-01-15 6:34 ` Johannes Schindelin
2016-01-15 14:53 ` Ramsay Jones
2016-01-15 6:54 ` Johannes Sixt
2016-01-15 14:55 ` Ramsay Jones
2016-01-14 18:52 ` Eric Sunshine
2016-01-15 6:35 ` Johannes Schindelin
2016-01-15 17:26 ` Junio C Hamano [this message]
2016-01-19 9:40 ` Johannes Schindelin
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=xmqq60yukb49.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=blume.mike@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.com \
--cc=sunshine@sunshineco.com \
--cc=tboegi@web.de \
/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.