Aw: Re: Re: [Bug report] 'git status' always says "Your branch is up-to-date with 'origin/master'"

From: Thomas Ackermann <th.acker@arcor.de>
Date: Jan 6, 2014, 09:08 UTC
Message-ID: <1283978462.720554.1388999328222.JavaMail.ngmail@webmail15.arcor-online.net>
In-Reply-To: <CAGyf7-FX1sPjwvKdxeEXopffFPiftgDRqoe7NRWyM1Cm=5n6Sw@mail.gmail.com>

Show 8 quoted lines

> 
> Unfortunately that's not true. In repo_b your ref for origin/master
> has not moved. It has remotely (meaning refs/heads/master in repo_a
> has moved), but git status is not hitting the remote to find out; it
> only looks at the local state. To see what I mean, run git fetch in
> repo_b. Once you do that, you'll see that git status correctly reports
> you're behind.
>

OK; my expectation was, that the remote is checked for this ... I see that this feature is useful for all non-trivial use cases where you have several branches beside master for which the remotes will be updated by git fetch. But for the simple use case where you only have a master branch I consider it not really helpful and - at least for me - misleading.

--- Thomas