19 ms·
> With Jujutsu, you'd instead use jj split to split the working copy commit into two commits. This is more confusing? Often times when debugging/writing a fix
by omegalulw 5y ago
> With Jujutsu, you'd instead use jj split to split the working copy commit into two commits.
This is more confusing? Often times when debugging/writing a fix I would have extraneous code that I wouldn't want to commit. With an index I'm always sure if what I commit, but with this workflow you have to keep track of such stuff all the time and if you forget that stuff makes it in?
Not to mention that another benefit of an index is being able to change commits and git replaying your working diff.
- em-bee 5y agoyeah, i feel this is going to bother me, or at least be difficult to get used to. i often have temporary files that i do not want to commit, nor do i want to add them to .gitignore (because i want to commit them later) but then, i'll have to spend some time using jj split. if it is powerful enough then maybe the end result is just that those files only live in the last commit. also, what happens on push? i'd never ever want the working copy to be pushed to the remote repo. i could not find anything in the documentation about that. (according to the answer here: https://news.ycombinator.com/item?id=30399554 https://news.ycombinator.com/item?id=30399554 the working copy is not supposed to be pushed)
- joseph8th 5y agoYah... I have a long-standing habit of commenting `TODO` for some debugging or WIP code. Then, before I commit, I can just do `git diff | grep TODO` and see all the new TODOs I've added.