[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 12:24:14 -0400

Laird Nelson wrote:

> ----- Original Message -----
> From: "Derek R. Price" <address@hidden>
> > The example is three
> > teams at the same company sharing a CVS repository.  Two use 'cvs
> watch' by
> > default and one does not.
> So how about making it part of the modules file?

You'd certainly be creating some complex cases.  If a dir was a member
of two modules, one with watch on and one with watch off, which do you
use?  If two modules are members of a larger module, and all three have
watch settings, does the lower granularity setting override, or no?

If you could find a way to implement this that wouldn't screw up
backwards compatibility, I'd certainly have no objections, but again,
why bother?  If you have your granularity such that you don't want
'watch on' inherited from $CVSROOT, you have to type 'cvs watch on' once
at the toplevel of the new module (where module=directory in the simlest
case) and everything below will have watch on from then on.  I'd think
that that was easier than adding a module description to the modules


Derek Price                      CVS Solutions Architect ( )
mailto:address@hidden     OpenAvenue ( )
It's always darkest before dawn. So if you're going to steal the
neighbor's newspaper, that's the time to do it.

reply via email to

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