From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>,
Mathias Lafeldt <mathias.lafeldt@gmail.com>,
Alexander Sulfrian <alexander.sulfrian@fu-berlin.de>,
Dennis Kaarsemaker <dennis@kaarsemaker.net>,
John Keeping <john@keeping.me.uk>,
Konstantin Koroviev <kkoroviev@gmail.com>,
"Mark A. Grondona" <mark.grondona@gmail.com>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
Maxim Bublis <b@codemonkey.ru>,
Richard Hansen <rhansen@rhansen.org>,
Roman Neuhauser <rneuhauser@suse.cz>,
Simon Chiang <simon.a.chiang@gmail.com>
Subject: Re: [ANNOUNCE] Sharness v1.0.0
Date: Tue, 14 Jun 2016 14:50:29 -0700 [thread overview]
Message-ID: <xmqqy467784a.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160614214655.GA22334@sigill.intra.peff.net> (Jeff King's message of "Tue, 14 Jun 2016 17:46:55 -0400")
Jeff King <peff@peff.net> writes:
> Yeah, I don't think it has kept up with our work. My statement above was
> "I don't think we'd _ever_ want to consider sharness the upstream, even
> if it were up to date", but obviously there would be a lot of work to
> even get it there.
I actually was a lot more optimistic when they started, and if it
were up to date, I would have at least tried to see what the damage
to our t/ part will be if we swapped t/test-lib{,-functions}.sh with
it, which was the original reason why I took a look until I found
out that it did not have some things.
prev parent reply other threads:[~2016-06-14 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 19:34 [ANNOUNCE] Sharness v1.0.0 Christian Couder
2016-06-14 19:48 ` Stefan Beller
2016-06-14 21:13 ` Christian Couder
2016-06-15 9:03 ` Mathias Lafeldt
2016-06-14 21:34 ` Jeff King
2016-06-14 21:43 ` Junio C Hamano
2016-06-14 21:46 ` Jeff King
2016-06-14 21:50 ` 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=xmqqy467784a.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=alexander.sulfrian@fu-berlin.de \
--cc=b@codemonkey.ru \
--cc=christian.couder@gmail.com \
--cc=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=kkoroviev@gmail.com \
--cc=mark.grondona@gmail.com \
--cc=mathias.lafeldt@gmail.com \
--cc=peff@peff.net \
--cc=rhansen@rhansen.org \
--cc=rneuhauser@suse.cz \
--cc=simon.a.chiang@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.