From: Thomas Rast <trast@student.ethz.ch>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Michael Haggerty" <mhagger@alum.mit.edu>
Subject: Re: tr/pty-all (Re: What's cooking in git.git (Dec 2011, #04; Tue, 13))
Date: Wed, 14 Dec 2011 17:17:14 +0100 [thread overview]
Message-ID: <201112141717.15021.trast@student.ethz.ch> (raw)
In-Reply-To: <20111214070916.GA14954@elie.hsd1.il.comcast.net>
Jonathan Nieder wrote:
> Junio C Hamano wrote:
> > Will merge to 'next' after taking another look.
>
> The middle commit looks good. The bottom commit could be improved as
> discussed at [1], but I guess that can happen in-tree.
>
> However, the top commit ("test test-terminal's sanity") still does not
> seem right to me.
I wasn't under the impression that we were done with this, either :-)
> It makes the same test run three times. Probably I should send an
> alternate patch to get that sanity-check to run once, but I am also
> not convinced the sanity-check is needed at all --- wouldn't any test
> that is relying on output from test_terminal act as a sanity check for
> it already?
It didn't. Or more precisely, Michael Haggerty ran into the behavior
of
git rev-parse ... | while read sha; do git checkout $sha; make test; done
couldn't make any sense of it, and reported it on IRC. So in some
sense, it took infrequent circumstances and two developers' time; next
time around I'd prefer it to be detected automatically.
> As an aside, I also still believe that running "git shortlog" without
> explicitly passing "HEAD" when testing how it reacts to [core] pager
> configuration was a bug and a distraction, hence the patch at [2].
Why not. Some other test should verify how shortlog reacts to the
tty-ness of stdin, but that's yet another direction.
> I also find Jeff's patch [3] appealing.
Me too, though wonder whether feeding a file full of garbage wouldn't
be better, so as to trip up commands that try to read only from a
non-tty stdin.
> [1] http://thread.gmane.org/gmane.comp.version-control.git/186923/focus=186944
> [2] http://article.gmane.org/gmane.comp.version-control.git/186932
> [3] http://article.gmane.org/gmane.comp.version-control.git/186936
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2011-12-14 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 1:19 What's cooking in git.git (Dec 2011, #04; Tue, 13) Junio C Hamano
2011-12-14 7:09 ` tr/pty-all (Re: What's cooking in git.git (Dec 2011, #04; Tue, 13)) Jonathan Nieder
2011-12-14 16:17 ` Thomas Rast [this message]
2011-12-14 17:42 ` Junio C Hamano
2011-12-14 23:07 ` Jeff King
2011-12-14 23:21 ` Jeff King
2011-12-14 23:31 ` Jonathan Nieder
2011-12-15 0:25 ` Jeff King
2011-12-15 0:50 ` Jeff King
2011-12-15 3:23 ` Junio C Hamano
2011-12-15 6:55 ` Jeff King
2011-12-15 18:19 ` Junio C Hamano
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=201112141717.15021.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).