On 6 Mar 2000, at 9:37, Noel L Yap wrote:
> [EMAIL PROTECTED] on 2000.03.03 16:04:27
> >[ On Friday, March 3, 2000 at 11:18:50 (-0500), Noel L Yap wrote: ]
> >> Subject: Re: removing the need for "cvs add file" to contact the server....
> >>[SNIP]
> >> What do you think it does in order for
> >> it to work on future files?
> >
> >That is irrelevant. We're (or at least I am) talking about a concept
> >here, not its implementation.
> >
> >Conceptually "cvs watch" operates only on files, regardless of how they
> >are specified, just as "cvs ci" and other similar workspace sub-commands
> >operate only on files.
>
> OK, but regardless of the implementation, "cvs watch" must operate on
> directories in order to achieve this future inheritence.
Noel, How about trying this concept:
cvs watch evaluates 'cvs watch dir' whenever it needs to, so that new files
will
also be watched.
If you think of it that way, then you can see that it is no different than
'cvs commit dir' - which will commit changed/added files now and will also
commit files added/changed in the future, when it is executed again.
> Also, I just thought of a couple of cases that might need discussion:
> echo "dir" >.cvsignore
> mkdir dir
> cd dir
> touch file
> cvs add file
>
> and, a little different:
> echo "dir0" >.cvsignore
> mkdir -p dir0/dir1
> cd dir0/dir1
> touch file
> cvs add file
>
> Where, if anyplace, will CVS admin subdirectories get created?
>
Now *this* is constructive.
Greg, is this a case you have covered?
And have you coded any of this yet?
I'm quite eager to see it.
Mike
--
Mike Little
Share what you know. Learn what you don't.
ServicePOWER Business Solutions Ltd
home: [EMAIL PROTECTED]
