Nope, Frank. Allan is dead on in this case. I check the code out all the time. The problem is never read in this environment, but just write privileges.
There are systems that work the way you are thinking, and you probably use those at work. On Apr 7, 2005 10:33 AM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > On Thu, April 7, 2005 1:15 pm, Fogleson, Allen said: > > Huh? > > > > SVN is like CVS. You don't lock files when you check them out. I can't > > write to the svn repository but almost anyone can do an anonymous > > checkout, do updates (one way, to their copy of the repository). > > Otherwise it would be near impossible to write patches :) > > This is a lesson for me. I thought one of the primary purposes of any > source control system was to disallow concurrent modifications (unless > specifically allowed). The whole point of checking code out, as I > understand it (and use it on a daily basis) is to be sure I am the only > one modifying a particular source file at any given time. Sure, you can > always get the latest code from the repository and modify it to your > hearts' content, but can you apply your changes anonymously then? Perhaps > I have some stuff to learn here, but that is completely contrary to how we > use source control here. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
