RE: 'cvs watch on' patch

[Jim.Hyslop]

lawrence.jones@ugs.com wrote:
> Jim Hyslop writes:
> > 
> > While I'm at it, I think I'll look into the discrepancy between 
> > documented behaviour of the 'cvs watch' commands and the actual 
> > behaviour. According to the documentation, if "files" mentions any 
> > directories, it should set the default attributes for that 
> directory; 
> > cvs 1.11 only sets default attributes if "files" is 
> omitted. I don't 
> > object to the behaviour, but it will make it difficult to 
> implement any 
> > "rwatch" command in the future, since the rwatch will 
> require a file or 
> > module specification.
> 
> Which is why I think the documentation is right and the code is wrong.
Agreed.

Would there be any use-cases where I'd want to watch a directory, but not
anything added afterwards? For example:

cvs watch add someDir

I care about someDir, but not about files or directories that might be added
later, such as:

mkdir someDir/whoCares
cvs add someDir/whoCares

In this case, we could add a flag to suppress setting default attributes for
subdirectories, e.g.:

cvs watch add --NoSetDefault someDir

Can anyone think of any situations where this would be useful? It doesn't
seem terribly useful to me, but there may be specific use-cases I can't
think of, where it would be handy. Or maybe a --NoInherit flag: I want to
know when this directory changes (files are added or removed), but don't
automatically propagate the default into new directories. Thoughts? (Any
changes like this would, of course, go into the feature branch.)

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )