From: Harald Nordgren Date: Sun, 18 Oct 2026 15:19:46 GMT Subject: Re: [PATCH] branch: let inherit track a remote-tracking start point Message-ID: In-Reply-To: > For me it depends on what I'm forking from. If I create a branch on my > desktop, push it to my server and then create a local branch from that > on my laptop, I normally want the new branch to track something like > origin/master rather than the starting point. However, if I create a new > branch from origin/master then I do want to track the starting point. So > it is not clear to me that the behavior proposed here is better than the > current behavior, but equally I don't think it is any worse. Having some > way of saying "set up tracking when the starting point matches one of > these patterns" might be useful, but I find the tracking options to "git > switch -c" so confusing I normally just run "git branch > --set-upstream-to" afterwards to set the upstream I want. I don't actually use 'git switch -c', I just used that in the example because it's the *modern* way to do things. In reality I always run 'git checkout -b'. I agree about `set-upstream-to`, there is probably no single terminal command that I run more than git branch --set-upstream-to=origin Your example got me thinking. Maybe we should go the other way? If we can inherit from the branch we are coming from, should we do that as first prio? Because of the `--set-upstream-to=origin` usage, we will likely already be tracking the right one. So git checkout -b first_branch git branch --set-upstream-to=origin/master git checkout -b new_branch origin/another_branch could give us a 'new_branch' that tracks what 'first_branch' tracked, i.e. 'origin/master'. Maybe as a fallback, we could have the new behavior from my v1, so if 'first_branch' has no tracking branch, then git checkout -b first_branch git checkout -b new_branch origin/another_branch falls back to 'new_branch ' tracking 'origin/another_branch' instead? Or not, maybe this fallback is just bad? Harald