3 ms·
Interesting to see someone doing this, it often comes up that we should actually have more levels of version control granularity than merges and commits. Just n
by fulafel 5y ago
Interesting to see someone doing this, it often comes up that we should actually have more levels of version control granularity than merges and commits. Just need an application of AI to generate good commit messages here :)
- exdsq 5y agoThat could be interesting but the right structure (off the top of my head) would be a hierarchical layer - not this flat monstrosity!
- globular-toast 5y agoI use the "undo" functionality in my editor. In emacs it's a complete tree of changes so you can't really lose anything.
- tom_ 5y agoTrue, but that's no guarantee you'll ever be able to actually find it.
- fulafel 5y agoIt's something but it's ephemeral and not shareable. You can't reconstruct how a piece of code got written weeks later, to eg recover some debug helpers you deleted without committing because you thought you were done with debugging it. But thanks for the tip about Emacs undo tree, didn't know about that. With some add-ons you can apparently eg find undoable changes for only some region of a buffer, etc.
- mssdvd 5y agoYou can also setup undo-tree to show a diff for every change.
- karthink 5y ago> With some add-ons you can apparently eg find undoable changes for only some region of a buffer, etc. This is built into Emacs (no add-ons needed). Calling undo with a region selected undoes changes only in that region.
- astrange 5y agoI actually disagree with this because I think you should try to have the project even vaguely work at each commit, so "git bisect" will work. But maybe each commit could be a log of keystrokes instead of a text diff.