From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: shortening the git test suite
Date: Mon, 02 Jul 2018 00:56:14 -0400 [thread overview]
Message-ID: <87po06qlqp.fsf@netris.org> (raw)
In-Reply-To: <87r2ko6pby.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 30 Jun 2018 21:34:25 +0200")
Ricardo Wurmus <rekado@elephly.net> writes:
> git takes a very long time to build, because it has an extensive test
> suite. Most of the time is spent in running the SVN interoperability
> tests, though, which are not really all that interesting for most uses
> of git.
>
> The Makefile says this:
>
> # Define NO_SVN_TESTS if you want to skip time-consuming SVN interoperability
> # tests. These tests take up a significant amount of the total test time
> # but are not needed unless you plan to talk to SVN repos.
>
> What do you think about disabling the SVN tests in the git package?
My preference would be to keep the SVN tests enabled, but it's not
something I feel very strongly about.
Thanks,
Mark
next prev parent reply other threads:[~2018-07-02 4:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 19:34 shortening the git test suite Ricardo Wurmus
2018-06-30 23:52 ` Gábor Boskovits
2018-07-01 13:54 ` Marius Bakke
2018-07-05 9:28 ` Ricardo Wurmus
2018-07-02 4:56 ` Mark H Weaver [this message]
2018-07-02 8:39 ` Gábor Boskovits
2018-07-05 9:28 ` Ricardo Wurmus
2018-07-05 8:44 ` Chris Marusich
2018-07-05 9:21 ` Ricardo Wurmus
2018-07-06 9:46 ` Gábor Boskovits
2018-07-06 18:19 ` Mark H Weaver
2018-07-06 21:05 ` Ludovic Courtès
2018-07-07 8:07 ` Gábor Boskovits
2018-07-07 16:44 ` Mark H Weaver
2018-07-07 21:37 ` Ricardo Wurmus
2018-07-08 22:41 ` Mark H Weaver
2018-07-09 7:47 ` Ricardo Wurmus
2018-07-11 12:46 ` Ludovic Courtès
2018-07-12 9:27 ` Chris Marusich
2018-07-08 1:29 ` Mike Gerwitz
2018-07-06 21:09 ` Automatic branch merging upon build completion Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po06qlqp.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).