Basically ....
I did a "cvs watch on" and then a "cvs watch add -a all"; (all
captures (edits, unedits, commits). The problem is that when
I do a "cvs watch off," and "cvs watch remove -a all," I still
get continuous notifications, even on different CVS repositories
that I didn't even set the watch for (very strange??). Is there a
better way to send e-mail notification and at least capture
commits and edits ???
-----Original Message-----
From: Noel L Yap [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 02, 2000 8:55 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: cvs watch
I've never really done "cvs watch off" so the following is a guess. Also,
I'm
assuing you used "cvs watch on" to turn watches on.
The behaviour of "cvs edit" (at least when "cvs watch" is on) is to place
temporary watches on the files being edited. When "cvs watch off" is given,
I
think those temporary watches may still exist thereby causing notifications.
Edits occurring after "cvs watch off" should not cause any notifications.
Noel
[EMAIL PROTECTED] on 03/01/2000 07:06:00 PM
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: cvs watch
Has any experienced a bug with "cvs watch" where once
it is enable it never shuts off unless the command in the "notify"
admin file is commented? I try using "cvs watch remove" and then
"cvs watch off" but it nevers shuts down the notification between
users. Any Insight ??
Jesse
