On 10/1/07, David Waite <dwaite@gmail.com> wrote:
> The pain with 'mark for edit' is that it means there are steps between you
> and your goal; you think about a change, you start to work on it and - oh,
> the file is read only. Let me go play with a tool to tell it what I plan to
> do, so I can actually put my ideas in motion.
I have to admit, I thought this would be the case too. Then I came to
google, where we use perforce every day, and after two years it really
doesn't seems like a big deal at all. It's not noticeable. I suspect
other svn-committers-who-are-googlers would agree with me.
Remember that we have to use 'svn' to add, delete, copy, move files.
Editing files is the one bizarre exception that you don't have to tell
svn about, and it's an exception that we have to explicitly teach to
svn-newbies. I suspect the reason so many svn developers shutter at
the idea of a mandatory 'svn edit foo.c' command is because they were
raised on cvs. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 1 15:16:23 2007