git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Cristian Tibirna <ctibirna@giref.ulaval.ca>, git@vger.kernel.org
Subject: Re: fetch --no-tags with and w/o --all
Date: Wed, 06 Mar 2013 16:41:44 -0800	[thread overview]
Message-ID: <7vhakonirb.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130307002038.GA31571@sigill.intra.peff.net> (Jeff King's message of "Wed, 6 Mar 2013 19:20:38 -0500")

Jeff King <peff@peff.net> writes:

> On Wed, Mar 06, 2013 at 01:56:01PM -0800, Junio C Hamano wrote:
>
>> Cristian Tibirna <ctibirna@giref.ulaval.ca> writes:
>> 
>> > Hello
>> >
>> > $ git --version
>> > git version 1.7.10.4
>> >
>> > $ git fetch origin --no-tags
>> > does what it says
>> >
>> > $ git fetch --all --no-tags
>> > still gets all the tags from the remote.
>> >
>> > Is this known?
>> 
>> Because --all (or --multiple) to iterate through all remotes
>> does not pass accept any command line refspecs, using these options
>> with --no-tags and/or --tags should be diagnosed as an error, but it
>> appears that the error checking is not done.
>
> Or we could just pass them through. Looks like this was already fixed by
> 8556646 (fetch --all: pass --tags/--no-tags through to each remote,
> 2012-09-05), which is in v1.7.12.2 and higher.

;-)  No wonder this looked somewhat familiar.

  reply	other threads:[~2013-03-07  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 21:33 fetch --no-tags with and w/o --all Cristian Tibirna
2013-03-06 21:56 ` Junio C Hamano
2013-03-07  0:20   ` Jeff King
2013-03-07  0:41     ` Junio C Hamano [this message]
2013-03-07  1:08       ` Jeff King

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=7vhakonirb.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=ctibirna@giref.ulaval.ca \
    --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).