4 ms·
I love the index, and often have "uncommitted" stuff lying around. jj makes doing this easier because you represent the index as an unnamed commit, and everythi
by steveklabnik 1mo ago
I love the index, and often have "uncommitted" stuff lying around. jj makes doing this easier because you represent the index as an unnamed commit, and everything just works, as opposed to needing to manage the index vs committed changes with separate tools.
- 1718627440 1mo agoThe absence of "needing to manage the index" is what breaks my workflow.
- steveklabnik 1mo agoWhat I mean is, you manage the index with the same commands that you manage commits with. The emphasis is on "with separate tools" not "manage the index". I am super curious as to what you mean specifically, but I also know that getting into details can be annoying, so if you have some specifics I'd love to hear more about them. I loved git's index so this isn't coming from a place of "the index sucks and you shouldn't care about it" it's "I think jj executes the index better than git does actually". But also if you don't, that's fine by me too, if you like a tool you should continue to use it. (I never set autosquash either)