2 ms·
Oddly enough I've always found command-line SVN lacking. Visual indicators seem to take version control to a much greater level. Eg, if I see an odd emblem on
by nailer 18y ago
Oddly enough I've always found command-line SVN lacking. Visual indicators seem to take version control to a much greater level.
Eg, if I see an odd emblem on something I don't remember modifying recently, I can inspect and diff. It could be some minor string fixes, or something more substantial. Either way, rather than doing a whole-tree commit (which wouldn't include a comment for the file I didn't remember editing), I'll now do a granular commit to that single file with an appropriate message.
- asjo 18y agoI've found the Subversion interface for Emacs (psvn - http://www.emacswiki.org/emacs/?SvnStatusMode http://www.emacswiki.org/emacs/?SvnStatusMode) very useful for this kind of overview, inspection and "selective" commits.
- sctb 18y agoMy experience has shown the opposite -- the worst programmers to work with on a project are the ones using Tortoise*. I've noticed more missed files in commits and poor branch management with Tortoise users than with command-line users. Of course, this is mere correlation rather than causality.
- neilc 18y agoI've never found much of a need for a GUI for version control -- especially with SVN, which has such a simple model (visualizing the revision graph for something like Monotone is useful, because it can become complex). Viewing diffs is trivial from the command-line, for example, and faster than using a GUI.
- nailer 18y agoFor me diffs are more viewable with decent visualization. '14c57' doesn't compare so much with a visual expansion marker connecting the previous and current states.