From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: Brandon Williams <bmwill@google.com>, git@vger.kernel.org
Subject: Re: Re* Is t5601 flaky for anybody else?
Date: Sun, 22 Oct 2017 15:06:26 +0530 [thread overview]
Message-ID: <1508664986.6715.4.camel@gmail.com> (raw)
In-Reply-To: <20171017210833.n5vgly7z2zi5dhuh@sigill.intra.peff.net>
On Tue, 2017-10-17 at 17:08 -0400, Jeff King wrote:
> On Wed, Oct 18, 2017 at 06:02:59AM +0900, Junio C Hamano wrote:
>
> FWIW, I can't replicate the problem on either "master" or "pu". I wonder
> why.
>
Neither can I. I tried running t5601 on "master" and on "pu" after
reverting the patch found in this thread. Both ran successfully without
issues.
--
Kaartic
prev parent reply other threads:[~2017-10-22 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 5:04 Is t5601 flaky for anybody else? Junio C Hamano
2017-10-17 17:10 ` Brandon Williams
2017-10-17 21:02 ` Re* " Junio C Hamano
2017-10-17 21:08 ` Jeff King
2017-10-22 9:36 ` Kaartic Sivaraam [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=1508664986.6715.4.camel@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).