> Obviously you guys have more experience in dealing with version control
> systems as well as with adding new features to Subversion. I know just one
> thing for sure: I'm a die hard CVS fan (even though I don't know all its
> features) who has to use Perforce because of how SourceMage project is
> hosted, and editing a file list before committing is one of the features
> I actually appreciate. I think it's logical because it allows productive use
> of something that is static in CVS: list of files that have changed.
I think this boils down to whether `svn' should offer a nice UI
or whether it should concentrate on providing clean semantics.
For example, in the case of CVS, I also like to see the list of files before
I commit them, but I don't rely on the `cvs' command-line client for that,
but on the PCL-CVS front-end instead.
Also, when it comes to partial commits, the file granularity is often
not sufficient in my experience, so I need something more sophisticated
than what you suggest.
OTOH, I don't care at all how `svn commit' behaves when it runs $EDITOR
because I never use it in this way (I always write the message somewhere
else first and pass it as an argument). I tend to see such "niceties" as
either baggage or annoyances (when a batch process ends up trying to
execute $EDITOR because of some mistake somewhere), but if it can be
convenient for someone...
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 21:39:41 2003