Re: Tag locking change

[Noel Yap]

--- "Greg A. Woods" <address@hidden> wrote:
> > and lots of people complained about it because
> tagging large trees can
> > take a long time and no one can even do checkouts
> or updates while the
> > tag is in progress.
> 
> That's life.  Tell them to get a faster disk
> subsystem, or get over it!  :-)

This may be life with CVS due to a flawed design, but
it need not be life in general.  Subversion looks like
it's fixed this problem since tags and branches are
created in constant time.

> (running such long-running commands on the server
> instead of remotely
> from a client might help too)
> 
> Such complaints really have no significance in
> relation to correctness
> and maintenance of repository integrity.  Obviously
> users could still
> erroneously commit related changes with separate
> commands and still end
> up with partially tagged changes, but that's a user
> error and not one
> caused by poor locking strategies in the system.  If
> the users don't
> make such errors then the system shouldn't screw up
> behind their backs.

Again, this is, IMHO, due to flawed design. 
Subversion locks the entire tree thereby guaranteeing
atomicity of checkins.

To be fair, Subversion (still in alpha) is the first
VC tool I've seen that properly addresses these
issues.  It does so by versioning the entire tree, not
individual elements.

Noel

__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com