3 ms·
> You can use git commit --fixup to record what you want to change in an earlier commit. jj just does it correctly by default. > rerere jj just does it corre
by baq 1y ago
> You can use git commit --fixup to record what you want to change in an earlier commit.
jj just does it correctly by default.
> rerere
jj just does it correctly by default.
> As written elsewhere: git rebase --update-refs. If you want to do it manually git rebase --onto.
jj just does it correctly by default.
defaults matter.
- 1718627440 1y ago>> git commit --fixup > jj just does it correctly by default. JJ adds changes to random old commits instead of the newest one? Yikes. > rerere by default Takes space and time. > --update-refs by default Maybe sensible, don't need it most of the time.
- baq 1y ago> JJ adds changes to random old commits instead of the newest one? Yikes. jj adds changes to the current commit, which is the staging area, which is the index, which is the working copy. I get you don't like it, no need to be an ass about it, but denying that it works is just that, denial. > > rerere by default > Takes space and time. doesn't take my time. I'll take it. > > --update-refs by default > Maybe sensible, don't need it most of the time. No reason to waste time thinking when it's needed.
- 1718627440 1y ago> no need to be an ass about it That wasn't what I meant, git --fixup is for changing earlier commits, you answered as if it didn't that's what I wanted to point out. (I tried to be sarcastic, because it was obvious that you didn't mean that.) >> Maybe sensible, don't need it most of the time. As in I want the opposite behaviour most of the time. That's why that is the default.