From: Eric Wong <e@80x24.org>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2016, #07; Mon, 25)
Date: Tue, 26 Jul 2016 07:14:43 +0000 [thread overview]
Message-ID: <20160726071443.GA24783@dcvr> (raw)
In-Reply-To: <6E620FEE-7149-4A01-9146-A480FD985499@gmail.com>
Lars Schneider <larsxschneider@gmail.com> wrote:
> On 26 Jul 2016, at 00:50, Junio C Hamano <gitster@pobox.com> wrote:
> >
> > * ew/git-svn-http-tests (2016-07-25) 2 commits
> > - git svn: migrate tests to use lib-httpd
> > - t/t91*: do not say how to avoid the tests
> >
> > Reuse the lib-httpd test infrastructure when testing the subversion
> > integration that interacts with subversion repositories served over
> > the http:// protocol.
> >
> > Will merge to 'next'.
>
> Do I understand correctly that this patch fixes $gmane/295291 ?
> Nice! Should we add "GIT_SVN_TEST_HTTPD=true" to the .travis.yml, then?
Maybe :)
Unfortunately, that currently causes the svn file:// tests (using the
same test numbers+files) to be skipped. We should probably define new
test numbers and figure out a way to be able to always run file:// and
http:// (and svn://) tests.
On a side note, svn:// ought to be easy since svnserve supports --inetd
and we can let the kernel bind a random port. We could be doing the
same with git-daemon --inetd, even...
prev parent reply other threads:[~2016-07-26 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 22:50 What's cooking in git.git (Jul 2016, #07; Mon, 25) Junio C Hamano
2016-07-26 6:55 ` Lars Schneider
2016-07-26 7:14 ` Eric Wong [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=20160726071443.GA24783@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@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.