[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tag locking change

From: Greg A. Woods
Subject: Re: Tag locking change
Date: Sun, 6 Oct 2002 19:24:31 -0400 (EDT)

[ On Sunday, October 6, 2002 at 18:01:01 (-0400), Larry Jones wrote: ]
> Subject: Tag locking change
> I've checked in a change to the [r]tag command to go back to locking
> one directory at a time (correctly, this time) rather than locking the
> entire tree for the whole time.

Is this really a good idea?  Do people who start a 'cvs co -r' or some
other command using the new tag too soon before an [r]tag is finished
deserve to lose (assuming by some strange quirk of concurrency that
their command catches up to the tag)?

(Forcing consistent use of the modules file at all times would allow a
module to be locked without so much overhead.... :-)

>  In the process, I noticed that the
> admin command also locks the entire tree, for no good reason that I can
> think of.  Can anyone else come up with one?  If not, I'll change it to
> lock one directory at a time, too.

Some 'cvs admin' options recursively muck with state that could have
some detrimental affect if it's not done "atomically", but people
probably shouldn't be using those options with CVS in the first place. :-)

                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]