3 ms·
Yeah, but not everyone wants to have their commit logs full "testing sample code 2" etc. Maybe you're profiling and you're trying out different pieces of code
by catch23 17y ago
Yeah, but not everyone wants to have their commit logs full "testing sample code 2" etc. Maybe you're profiling and you're trying out different pieces of code to see which ones might be faster -- happens all the time in javascript because browser implementations of javascript aren't identical. I don't do these intermediate commits otherwise my log would be a pain to read and 95% of the commit messages would be me testing out random code samples.
Another useful case for it is when you're just putting in a bunch of debugging statements that you don't want to be committed later. I find myself doing undo/redo all the time for doing stuff like this. I think a more advanced undo/redo would definitely help out.
- aaronblohowiak 17y ago>not everyone wants to have their commit logs full "testing sample code 2" etc That's why you squash the commits when you are done with the profiling. Squashing the commits makes it seem like just one commit (and one commit message) in the log. This way your log is clean, but you get the advantage of frequent saves. If you dont want to do this, you could probably hook up something with FUSE