Re: cvs commit confirmation (was: User interface proposal)

Karl Fogel wrote:
> > One of the things I like about Perforce is that default behavior
> > of "p4 submit" is that it drops you into an editor where you
> > can see what all you've changed. Files added, edited, and deleted
> > are listed (Perforce has no rename operation), and you can
> > edit the list while you're editing your log message.

> That's probably too far from the CVS conventions for most users to
> accept (also, CVS has a different, but okay, way of providing similar
> functionality).

Sounds like a good configuration candidate.
I think such a feature would be excellent!

> > As for "svn rm", I'd rather it be explicit, for the reasons others
> > have already cited. (I'd rather that "svn edit" be explicit, too.)
>
> The latter would cause a revolt, probably. :-)

Config issue :-) I prefer either way, myself.

> CVS working copies are
> editable the moment they appear on disk; if people had to issue a
> command before editing files in Subversion, they'd be surprised and
> almost certainly unhappy.

I generally work from read-only copies and make specific pieces
of it editable. I like that behavior.

Except for where it is too little benefit for too much work,
configure it :-) Personal taste & project-wide config files are great.
Received on Sat Oct 21 14:36:09 2006