Re: Update before commit

On Thu, 15 Feb 2007 08:30:16 -0800 (PST), lightbulb432
<veerukrishnan@hotmail.com> wrote:

>If it's the latter case, that sounds like a good plan for protection, but in
>huge projects with lots of developers and frequent commits, wouldn't you be
>doing update after update after update just to try to get in that one
>commit?

No. "svn update" will take you to the last committed version. "svn
commit" will then commit your changes. Yes, it is theoretically
possible someone could commit a change between your "update" and
"commit", but if other people are regularly making changes to the
files that you are also making changes too, then you've got bigger
problems than source code management.

Greg

-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org