git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Kevin Daudt <me@ikke.info>
Cc: Junio C Hamano <gitster@pobox.com>,
	"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 03:47:28 -0400	[thread overview]
Message-ID: <20170820074728.4dawjlnaufjdf4j5@sigill.intra.peff.net> (raw)
In-Reply-To: <20170817204312.GD3839@alpha.vpn.ikke.info>

On Thu, Aug 17, 2017 at 10:43:12PM +0200, Kevin Daudt wrote:

> > No, you are not misunderstanding anything.  The "pretend that we
> > immediately turned around and fetched" done by "git push" was
> > already breaking the predictability, but the change in 1.8.4 made it
> > even worse.  I am saying that going back to the old behaviour may be
> > one option to address the issue being discussed in this thread.
> 
> Ok. The reason I'm bring this up is because we often had to tell users
> in the irc channel that git fetch <remote> <branch> did not update the
> remote tracking branches, which confused them, so reverting back might
> reintroduce this confusion again.

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.

-Peff

  reply	other threads:[~2017-08-20  7:47 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 [this message]
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

  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=20170820074728.4dawjlnaufjdf4j5@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Magnus.Carlsson@arris.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ikke.info \
    /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).