RE: Fast version control while work proceeds

Quoth Ryan Schmidt <mailto:subversion-2005@ryandesign.com>:
> Subversion is not designed for that scenario. It's designed to help
> you with this workflow:
>
> 1. Start with an up-to-date working copy of (a part of) your
> repository.
> 2. Edit the working copy to fix a bug or implement a feature.
> 3. Commit the changes.
> 4. Update the working copy to receive changes from other developers.
> 5. Goto 2.

Minor quibble: 3 & 4 are usually the other way around. Unless you're
working in a private branch.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 16 22:30:50 2005