From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Jul 2011, #01; Wed, 6)
Date: Wed, 13 Jul 2011 15:12:35 -0700 [thread overview]
Message-ID: <7vd3hd6d9o.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vpqlmhoi0.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 06 Jul 2011 18:24:07 -0700")
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
fast-import: dumping crash report to /srv/project/git/git.git/t/trash
directory.t5800-remote-helpers/localclone/.git/fast_import_crash_16957
error: refs/remotes/origin/master does not point to a valid object!
error: Trying to write ref refs/heads/master with nonexistent object
0000000000000000000000000000000000000000
fatal: Cannot update the ref 'HEAD'.
not ok - 2 cloning from local repo
#
# git clone "testgit::${PWD}/server" localclone &&
# test_cmp public/file localclone/file
#
Stumped...
next prev parent reply other threads:[~2011-07-13 22:12 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 [this message]
2011-07-13 23:39 ` Jeff King
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=7vd3hd6d9o.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
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).