[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Repository know who has checkouts?
From: |
Derek R. Price |
Subject: |
Re: Repository know who has checkouts? |
Date: |
Fri, 06 Oct 2000 11:43:34 -0400 |
Noel L Yap wrote:
> What about getting rid of "cvs watch on/off" altogether and making this
> feature
> a configuration parameter inside CVSROOT/config?
I wouldn't object to a parameter to change the default watch status or the like
if
it didn't remove the old behavior, but it doesn't seem necessary. See below.
> The main difference I see is
> the granularity of "cvs watch on/off". However, I think teams tend to use
> "cvs
> watch on/off" for the entire repository, anyway. In fact, I think there may
> be
> a feature (or bug) in which new modules do not get "cvs watch on" if the team
> already deems all modules to have "cvs watch on".
I was just playing around and it seems that 'cvs watch' stores a 'fileattr' for
each directory as well as for each file and that this is where the watched
status
for new files and directories is inherited from. I also double checked that
this
can be applied to the top level directory, so why not:
cvs co -l .
cvs watch on
to make sure that new modules inherit the repository watch status?
As for the current granularity, I think it is important. The example is three
teams at the same company sharing a CVS repository. Two use 'cvs watch' by
default and one does not.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden OpenAvenue ( http://OpenAvenue.com )
--
I will never win an emmy.
I will never win an emmy.
I will never win an emmy...
- Bart Simpson on chalkboard, _The Simpsons_
- Re: Repository know who has checkouts?, (continued)
Re: Repository know who has checkouts?, Noel L Yap, 2000/10/06