> > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
