From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Carlsson\, Magnus" <Magnus.Carlsson@arris.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git fetch with refspec does not include tags?
Date: Thu, 17 Aug 2017 12:41:09 -0700 [thread overview]
Message-ID: <xmqqwp62f0dm.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170817142233.v2c534zh6wv7ttei@sigill.intra.peff.net> (Jeff King's message of "Thu, 17 Aug 2017 10:22:33 -0400")
Jeff King <peff@peff.net> writes:
> I think it's a bit more complex because "git pull" uses "git fetch"
> under the hood. In fact, your "git fetch origin master" is exactly what
> gets run when you do:
>
> git pull origin master
>
> That's maybe OK. But I think one-off pulls like:
>
> git pull https://example.com/repo.git master
>
> probably wouldn't want it. I'd have to give it some thought.
I agree with both. If you have named remote, you presumably are
keeping copies of their branches as remote-tracking branches, and it
may be fine to follow tags. An explicit URL used for one-off should
not grab anything but the named thing, I would think.
next prev parent reply other threads:[~2017-08-17 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1502960406180.9006@arris.com>
2017-08-17 9:02 ` git fetch with refspec does not include tags? Carlsson, Magnus
2017-08-17 9:28 ` Jeff King
2017-08-17 11:29 ` Carlsson, Magnus
2017-08-17 14:22 ` Jeff King
2017-08-17 19:41 ` Junio C Hamano [this message]
2017-08-17 19:38 ` Junio C Hamano
2017-08-17 20:22 ` Kevin Daudt
2017-08-17 20:38 ` Junio C Hamano
2017-08-17 20:43 ` Kevin Daudt
2017-08-20 7:47 ` Jeff King
2017-08-20 7:50 ` Jeff King
2017-08-20 15:51 ` 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=xmqqwp62f0dm.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Magnus.Carlsson@arris.com \
--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 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.