From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: 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 17:34:53 -0400 [thread overview]
Message-ID: <20160614213453.GA21560@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD0uvaB-2_CrXs2ZvoqLRHfCd8efA-S7-tE2Qa6Pn+rAAg@mail.gmail.com>
On Tue, Jun 14, 2016 at 09:34:17PM +0200, Christian Couder wrote:
> Version 1.0.0 of Sharness [1] -- the test harness library derived from
> Git's test lib -- is released.
Cool. Git's test harness is something I really miss having in other
projects. I'm glad this project exists. :)
> This release contains many upstream fixes and improvements from Git
> and a lot of specific user contributed features [2].
It looks like it takes some manual work to massage upstream improvements
into Sharness.
I don't think the Git project would ever want to say "sharness is the
upstream, and we are now just a user of it". But I wonder if we could
break down test-lib.sh to keep the Git-specific parts separate, which
would make it easier for sharness to pull the other bits as a whole.
I dunno. I guess it would depend on how invasive the patches were, but I
would not be opposed to such a thing. I suspect the separation might
actually make our test setup more clear.
-Peff
next prev parent reply other threads:[~2016-06-14 21:35 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 [this message]
2016-06-14 21:43 ` Junio C Hamano
2016-06-14 21:46 ` Jeff King
2016-06-14 21:50 ` 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=20160614213453.GA21560@sigill.intra.peff.net \
--to=peff@peff.net \
--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=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 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).