[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tag locking change
From: |
Larry Jones |
Subject: |
Re: Tag locking change |
Date: |
Mon, 7 Oct 2002 12:38:21 -0400 (EDT) |
Greg A. Woods writes:
>
> 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)?
Yes, I'd say they do. And they always have in the past. Locking the
whole tree was a fairly recent change in response to a report of lost
changes due to bugs in the previous directory-at-a-time locking method
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.
-Larry Jones
Santa's gonna skip this block for years. -- Calvin
- Re: Tag locking change, (continued)
- Re: Tag locking change, Jenn Vesperman, 2002/10/09
- Re: Tag locking change, Jenn Vesperman, 2002/10/09
- Re: Tag locking change, Mike Ayers, 2002/10/09
- Re: Tag locking change, Larry Jones, 2002/10/09
- Re: Tag locking change, Greg A. Woods, 2002/10/09
- Re: Tag locking change, Paul Sander, 2002/10/09
- Re: Tag locking change, Greg A. Woods, 2002/10/09
- Re: Tag locking change, Paul Sander, 2002/10/09
- Re: Tag locking change, Larry Jones, 2002/10/10
- Re: Tag locking change, Paul Sander, 2002/10/10
Re: Tag locking change,
Larry Jones <=
Re: Tag locking change, Patwardhan, Rajesh, 2002/10/07
Re: Tag locking change, Paul Sander, 2002/10/07
Re: Tag locking change, Paul Sander, 2002/10/09
Re: Tag locking change, erik . cumps, 2002/10/10