From: Junio C Hamano <gitster@pobox.com>
To: Mark Levedahl <mlevedahl@verizon.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG} git-fetch - won't fetch wildcarded tags
Date: Fri, 10 Aug 2007 21:14:15 -0700 [thread overview]
Message-ID: <7vd4xur9m0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46BD25FC.1050201@verizon.net> (Mark Levedahl's message of "Fri, 10 Aug 2007 22:59:08 -0400")
Mark Levedahl <mlevedahl@verizon.net> writes:
> git>git fetch /tmp/foo 'refs/tags/*:refs/tags/*'
> * refusing to create funny ref 'tags/*' locally
I think fetch's wildcard is effective only in the config file,
and this is not just tags. It would be nice if you could say
$ git fetch foo.bndl 'refs/*:refs/*'
prev parent reply other threads:[~2007-08-11 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 2:59 [BUG} git-fetch - won't fetch wildcarded tags Mark Levedahl
2007-08-11 3:25 ` Mark Levedahl
2007-08-11 4:14 ` Junio C Hamano [this message]
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=7vd4xur9m0.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mlevedahl@verizon.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).