Re: When does git check for branch-X being uptodate with origin/branch-X?

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 21, 2016, 20:47 UTC
Message-ID: <xmqqk2kvlfr5.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CA+39Oz4Atuv3N0QNj8o1SYgHzMUyES1QHUsWh-MdNiNr-xPM_w@mail.gmail.com>

Thomas Adam <thomas.adam22@gmail.com> writes:

Show 10 quoted lines

> On 21 March 2016 at 20:28, Jeff King <peff@peff.net> wrote:
>> 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.
>
> Thanks.  I understand how to use git-fetch, it's more a case of
> whether even printing that message is useful?  I appreciate it can
> only go on the cached value, but it is still misleading to print that
> in the case where the cache might not be up to date.

The real value of that message is "you haven't done anything on top of what you last fetched from there", so "you are up-to-date" may indeed be confusing, but I do not think of a better phrasing (other than spelling out "last fetched from there" part explicitly, which is quite a mouthful).