From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Kevin Daudt <me@ikke.info>, "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: Sun, 20 Aug 2017 08:51:51 -0700 [thread overview]
Message-ID: <xmqq8tie8cfc.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170820075001.gmsxeh3fh4f2topg@sigill.intra.peff.net> (Jeff King's message of "Sun, 20 Aug 2017 03:50:02 -0400")
Jeff King <peff@peff.net> writes:
> On Sun, Aug 20, 2017 at 03:47:28AM -0400, Jeff King wrote:
>
>> Yeah, I don't think we want to go back to the original behavior. I agree
>> that it is partially to blame for the inconsistency that started this
>> thread, but I think on balance it has saved much more confusion than it
>> has started. And we can address that inconsistency with better tag rules
>> (like the "autofollow if we wrote any real refs" thing).
>>
>> I don't have a patch for that yet, so if anybody feels like taking a
>> look, it would be much appreciated.
>
> Also: I don't think we've seen a patch yet for documenting the current
> auto-follow behavior. Even if we don't make a behavior change, let's
> not forget to improve that, which should be much less work. :)
Thanks for two thoughtful follow-ups.
prev parent reply other threads:[~2017-08-20 15:52 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
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 [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8tie8cfc.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Magnus.Carlsson@arris.com \
--cc=git@vger.kernel.org \
--cc=me@ikke.info \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).