Thomas Gummerer <t.gummerer@xxxxxxxxx> writes: > I didn't consider that, I think you are right, and the flag should > apply in that case as well. I think at that point we may as well pass > this flag through to the 'git branch' call, and let users set up > tracking if they want to, the same way it works in 'git branch'. OK, so tracking is set up by default in the current implementation of "git worktree" (even without your proposed update), but we will stop doing so, and instead take an explicit "--track" option (or "--no-track" to countermand an earlier "--track" on the command line and/or a default configured with branch.autosetupmerge) just like "git branch" does? I think that it is very sensible thing to make sure that "branch", "checkout -b" and "worktree", i.e. the three ways to create a branch to work on (the latter two being short-hands), behave consistently. Thanks.
