Hi, Thomas Ackermann wrote:
>> 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. [...] > 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. I see what you mean, and you're not the only one. Git follows a rule of "never contact another machine unless explicitly asked to using a command such as 'git pull' or 'git fetch'". To support this, it makes a distinction between (1) the remote-tracking ref origin/master and (2) the actual branch "master" in the remote repository. The former is what is updated by 'git fetch', and the latter is something git does not know about without talking to the remote server. What documentation did you use when first starting to learn git? Perhaps it can be fixed to emphasize the distinction between (1) and (2) earlier. Thanks, Jonathan -- 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
