From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2011, #01; Wed, 6)
Date: Wed, 13 Jul 2011 19:39:19 -0400 [thread overview]
Message-ID: <20110713233919.GA18273@sigill.intra.peff.net> (raw)
In-Reply-To: <7vd3hd6d9o.fsf@alter.siamese.dyndns.org>
On Wed, Jul 13, 2011 at 03:12:35PM -0700, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > * jk/clone-detached (2011-06-07) 4 commits
> > - clone: always fetch remote HEAD
> > - make copy_ref globally available
> > - consider only branches in guess_remote_head
> > - t: add tests for cloning remotes with detached HEAD
> >
> > Somewhat involved bugfix.
> > Will merge to "next".
>
> What is it in this series that causes t5800 to fail when merged to next, i.e.
>
> $ sh t5800-remote-helpers.sh -i -v
>
> expecting success:
> git clone "testgit::${PWD}/server" localclone &&
> test_cmp public/file localclone/file
>
> Cloning into localclone...
> fatal: Got feature command 'relative-marks' after data command
Isn't this the same breakage I reported in the initial series:
http://article.gmane.org/gmane.comp.version-control.git/174999
The discussion of which led to my remote helper fixes here:
http://article.gmane.org/gmane.comp.version-control.git/175217
But then the latter series got picked up and merged into Sverre's
sr/transport-helper-fix branch. I'm not sure what the current status of
that series is.
-Peff
next prev parent reply other threads:[~2011-07-13 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 1:24 What's cooking in git.git (Jul 2011, #01; Wed, 6) Junio C Hamano
2011-07-13 22:12 ` Junio C Hamano
2011-07-13 23:39 ` Jeff King [this message]
2011-07-15 22:15 ` Sverre Rabbelier
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=20110713233919.GA18273@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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).