Tymek Majewski <tmaj@xxxxx> writes: > Hello gurus! > > I looked at https://git-scm.com/community but I failed to find a > place to send feature requests to. > > Q: How to submit a feature request (rather than a bug)? Sending it here, which you did, is how ;-) > Reasoning: > > I believe that if the git checkout message > "Your branch is up to date with 'origin/branch_name_here'" > was > "Your branch is up to date with the *local* branch 'origin/branch_name_here'" > it would make it clearer to new users what is happening. I would be sympathetic to the above, if you did not say "local" and instead say "remote-tracking". A local branch is what you can check out and grow its history by making a commit while it is checked out. Those refs that are updated when you fetch and/or pull from the remote repository in order to keep track of the branches they have are called remote-tracking branches. Because this message is something people see every day when they run "git checkout", I am not sure if the extra explanation is warranted or merely annoying, as "origin/branch" notation is used sufficiently often for the users to grow accustomed to seeing it and knowing what it is, and after all no user will stay to be a newbie forever. Another reason why I am somewhat hesitant to endorse the rephrasing is because the name of a remote-tracking branch in the real life tends to be longer than just 'origin/master'. We must keep the message that comes before the name of the remote-tracking branch short in order to make it easier to read the message for the users. So... I dunno.
