From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Mathias Lafeldt <mathias.lafeldt@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Sharness - Test library derived from Git
Date: Fri, 20 Jul 2012 13:45:26 +0200 [thread overview]
Message-ID: <vpq7gtyr6zt.fsf@bauges.imag.fr> (raw)
In-Reply-To: <CAMFa-2gRWRKgj140i1q9iux=eC6nWxfdUPPhb42xAG1Gr7e4vA@mail.gmail.com> (Mathias Lafeldt's message of "Fri, 20 Jul 2012 12:18:51 +0200")
Mathias Lafeldt <mathias.lafeldt@gmail.com> writes:
> On Tue, Jul 17, 2012 at 8:31 PM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>
>> Perhaps to avoid duplication we could move to this and keep
>> Git-specific function in some other file.
>
> That would be fantastic! From a technical point of view, it would make
> a lot of sense to join forces here.
Seems to be a reasonable goal, yes. The test harness in Git keeps
improving, and Sharness is likely to improve also, it would be a pity to
have them diverge and not benefit from each other.
> How do you think would Sharness fit into the Git project? Is adding it
> as an external dependency an option?
It would be nice if the code sharing did not result in extra pain for
users and testers, so "external dependency" in the sense "not included
in git.git and ask the user to install it" is IMHO a bad idea.
Increasing the effort needed to run the testsuite means more people will
give up before running it :-(.
OTOH, having it leave in a subdirectory (e.g. $git/t/Sharness/), and
synchronize with stg like subtree merge would be nice for the user. We
already have something similar for gitk and git-gui, except that the
synchronization is normally one way (subprojects merged into Git, but
merging back changes that were made in git.git in these subprojects is
more painful).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-07-20 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 8:06 [ANNOUNCE] Sharness - Test library derived from Git Mathias Lafeldt
2012-07-17 18:31 ` Ævar Arnfjörð Bjarmason
2012-07-20 10:18 ` Mathias Lafeldt
2012-07-20 11:45 ` Matthieu Moy [this message]
2012-07-20 21:11 ` dag
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=vpq7gtyr6zt.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=mathias.lafeldt@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.