3 ms·
Yes, but not for a distant past (which is relative). Sometimes it is a revert to revision thing, sometimes I just remember a revision as a base for an ongoing r
by wruza 7y ago
Yes, but not for a distant past (which is relative). Sometimes it is a revert to revision thing, sometimes I just remember a revision as a base for an ongoing refactoring. It must be done in a branch, but when I work alone on my thing, I just break trunk and do commit broken tree at every evening (or at logical points, whichever comes first). Besides refactoring, nope, write-only style. All the variants of “knowledge base” code I need to reference to are in a separate dir/repo, ready to copy, re-experiment, revert back or commit. VCS is spacetime - you can use time and you can use space.
Also must confess that I never seen much profit for myself from commit messages apart from one-liners like “broken”, “savepoint” and “fixes to bar, uploaded foo”. If trunk has a problem, you just can blame and get an exact revision. If you search through a history, use a gui tool / ide that can fetch it quickly and compare to head, then bisect manually. I don’t make hundred-pagedown commits, so that’s easy enough.
For a future employer: that doesn’t mean I’m against or unable to make branches and write good commit messages. All above are just obvious shortcuts that my own “garage” projects tolerate with no downsides. Personally, I don’t get why some guys freely decide to break project rules when at work - and it was frustrating when they did it to me.