From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Thomas Adam <thomas.adam22@gmail.com>, git list <git@vger.kernel.org>
Subject: Re: When does git check for branch-X being uptodate with origin/branch-X?
Date: Mon, 21 Mar 2016 13:52:16 -0700 [thread overview]
Message-ID: <xmqqfuvjlfjz.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160321202810.GD32071@sigill.intra.peff.net> (Jeff King's message of "Mon, 21 Mar 2016 16:28:10 -0400")
Jeff King <peff@peff.net> writes:
> The message from checking is looking only at your local
> refs/remotes/fvwmorg/master branch, which is essentially a cache of what
> is in the actual remote repository.
Saying "cache of what is ..." would further confuse people, I am
afraid. We just keep a record of what we last observed and we do
not actively go out and update the remote tracking branch without
being told by the end user. "cache of what we saw there when we
contacted them the last time" is OK ;-).
>
> We never contact other repositories unless explicitly asked to by
> fetch, pull, push, etc. If you want to have the most up-to-date value
> without merging, you can just "git fetch" to update the tracking
> branches.
>
> -Peff
prev parent reply other threads:[~2016-03-21 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 20:21 When does git check for branch-X being uptodate with origin/branch-X? Thomas Adam
2016-03-21 20:28 ` Jeff King
2016-03-21 20:43 ` Thomas Adam
2016-03-21 20:47 ` Junio C Hamano
2016-03-21 20:50 ` Jeff King
2016-03-21 21:12 ` Thomas Adam
2016-03-21 21:18 ` Jeff King
2016-03-21 21:22 ` Thomas Adam
2016-03-21 21:50 ` Stefan Beller
2016-03-21 21:57 ` Junio C Hamano
2016-03-21 22:11 ` Stefan Beller
2016-03-21 22:42 ` Junio C Hamano
2016-03-21 23:18 ` Stefan Beller
2016-03-22 17:51 ` Philip Oakley
2016-03-21 20:48 ` Stefan Beller
2016-03-21 20:52 ` 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=xmqqfuvjlfjz.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=thomas.adam22@gmail.com \
/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).