Andreas Enge <[email protected]> writes: > Hello, > > Am Sun, Feb 15, 2026 at 05:37:35PM +0100 schrieb Yarl: >> You have a worktree at master in $MASTER. you want to fix package >> hello. > > for such small changes, why not simply work in a different branch in the > same worktree? I keep worktrees for branches with many changes, where > going back and forth amounts to lots of recompilation (for instance, the > team branches). Otherwise, I just use a branch in the master worktree. > > Andreas
> Am Sun, Feb 15, 2026 at 06:00:19PM +0100 schrieb Yarl: >> I tend to forget what I've been doing in which branch, that's probably >> why I over use worktrees: suppose I switch to see what is in a quite old >> branch, I realize it's quite old, I switch back, a lot to recompile, >> right? > > (You replied only to me, so I will continue this as a private > conversation.) my bad > In this case, I use "git log" a lot so as not to checkout the branch > I want to inspect. Then often there are only one or a few commits at the > top of the old branch. In this case, I sometimes branch off a new branch > from master and cherry-pick the interesting commits (for instance, for > "rebasing" an old pull request). > > Andreas I guess I've been using git badly.. I see your point. yarl
