From: Michael Haggerty <mhagger@alum.mit.edu>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: Git --reference bug(?)
Date: Wed, 19 Oct 2011 07:01:27 +0200 [thread overview]
Message-ID: <4E9E59A7.7070307@alum.mit.edu> (raw)
In-Reply-To: <CAK-xaQaUxJ5c_kN48g7-J9fosDv6awbAFQSFLpF2fA+hc-i-MA@mail.gmail.com>
On 10/19/2011 12:04 AM, Andrea Gelmini wrote:
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> /tmp/3.1 --reference /home/gelma/dev/kernel/linus/
> Cloning into /tmp/3.1...
> fatal: Reference has invalid format: 'refs/tags/3.1.1.1^{}'
> fatal: The remote end hung up unexpectedly
The upstream repo reports what look like non-reference references:
$ git ls-remote --tags
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git | head
5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c refs/tags/v2.6.11
c39ae07f393806ccf406ef966e9a15afc43cc36a refs/tags/v2.6.11^{}
5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c refs/tags/v2.6.11-tree
c39ae07f393806ccf406ef966e9a15afc43cc36a refs/tags/v2.6.11-tree^{}
26791a8bcf0e6d33f43aef7682bdb555236d56de refs/tags/v2.6.12
9ee1c939d1cb936b1f98e8d81aeffab57bae46ab refs/tags/v2.6.12^{}
9e734775f7c22d2f89943ad6c745571f1930105f refs/tags/v2.6.12-rc2
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 refs/tags/v2.6.12-rc2^{}
0397236d43e48e821cce5bbe6a80a1a56bb7cc3a refs/tags/v2.6.12-rc3
a2755a80f40e5794ddc20e00f781af9d6320fafb refs/tags/v2.6.12-rc3^{}
[...]
I've never seen this format before; is this the remote protocol for
peeled refs or maybe the behavior of an old version of git?
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-10-19 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 22:04 Git --reference bug(?) Andrea Gelmini
2011-10-19 5:01 ` Michael Haggerty [this message]
2011-10-19 6:21 ` Junio C Hamano
2011-10-19 6:25 ` Junio C Hamano
2011-10-19 6:33 ` Junio C Hamano
2011-10-19 6:55 ` Junio C Hamano
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=4E9E59A7.7070307@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=andrea.gelmini@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).