From: Mark Levedahl <mlevedahl@verizon.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: [BUG} git-fetch - won't fetch wildcarded tags
Date: Fri, 10 Aug 2007 22:59:08 -0400 [thread overview]
Message-ID: <46BD25FC.1050201@verizon.net> (raw)
git fetch does not seem to handle refs/tags/* refspecs, at least no from
bundles...
git>git bundle create /tmp/foo v1.5.2
<snip>
git>git ls-remote /tmp/foo
8b1e5575ab18757272e86c5ec7a10411bbaa3662 refs/tags/v1.5.2
git>git tag -d v1.5.2
Deleted tag v1.5.2.
git>git fetch /tmp/foo 'refs/tags/*:refs/tags/*'
* refusing to create funny ref 'tags/*' locally
Huh?
but...
git>git fetch /tmp/foo 'refs/tags/v1.5.2:refs/tags/v1.5.2'
* refs/tags/v1.5.2: storing tag 'v1.5.2' of /tmp/foo
tag: 8b1e557
What's going on? This is a severe limitation of the utility of bundles
to transmit tagged versions.
Mark
next reply other threads:[~2007-08-11 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 2:59 Mark Levedahl [this message]
2007-08-11 3:25 ` [BUG} git-fetch - won't fetch wildcarded tags Mark Levedahl
2007-08-11 4:14 ` 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=46BD25FC.1050201@verizon.net \
--to=mlevedahl@verizon.net \
--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 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).