From: Stephen Bash <bash@genarts.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Tags, Grafts, and Clones, oh my!
Date: Fri, 20 Aug 2010 10:40:50 -0400 (EDT) [thread overview]
Message-ID: <5054888.117464.1282315250235.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <20100820133925.GE9448@kytes>
> Thanks for the testcase! Offhand, it definitely looks like a bug. I'm
> investigating to figure out which part of the chain is at fault.
No problem. I was very happily to isolate it outside the large repo I was working with...
Contrary to my first e-mail, 'git checkout -b branchFoo tagFoo' doesn't solve the problem... My guess is I got lazy and did a "normal" local clone (no file URL) when I was testing.
Data from further testing:
- doing a "normal" local clone doesn't emit the error
- a remote clone over ssh does emit the error (so it's not just file:///)
- in a brand new repo (init'ed, not cloned) 'git fetch ../foo refs/tags/tagFoo:refs/tags/tagFoo' fails:
error: unable to find 28fffee... (sha of tag object)
- in a brand new repo 'git fetch ../foo refs/heads/branchFoo:ref/heads/branchFoo' succeeds, and correctly fetches tagFoo (where branchFoo is created via 'git checkout -b branchFoo tagFoo')
Thanks,
Stephen
next prev parent reply other threads:[~2010-08-20 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29380346.117285.1282264933599.JavaMail.root@mail.hq.genarts.com>
2010-08-20 0:54 ` Tags, Grafts, and Clones, oh my! Stephen Bash
2010-08-20 6:15 ` Ramkumar Ramachandra
2010-08-20 13:00 ` Stephen Bash
2010-08-20 13:39 ` Ramkumar Ramachandra
2010-08-20 14:40 ` Stephen Bash [this message]
2010-08-20 19:08 ` refs/original breaks git-clone for tags (was Re: Tags, Grafts, and Clones, oh my!) Stephen Bash
2010-09-07 23:14 ` refs/original breaks git-clone for tags Jonathan Nieder
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=5054888.117464.1282315250235.JavaMail.root@mail.hq.genarts.com \
--to=bash@genarts.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
/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.