This is very strange.  "cvs watch" only affects the directory hierarchy you used
it on.

You shouldn't have to do "cvs watch add -a all"; it's the default for "cvs watch
on".

You should probably have done the "cvs watch remove" before you did the "cvs
watch off".  I don't know if/how this affects your situation.

Are you sure the email is being sent by the notification mechanism?  Perhaps
it's being sent by the commitinfo/loginfo mechanism?

If you look at the CVS/fileattr files within the repo, what do you see?  If it's
not too large, can you attach it?

You can use commit scripts (ie commitinfo/loginfo mechanism) to send
notifications about commits.  The usual way to get per-file notifications about
commits, edits, and unedits is by doing a "cvs watch on" for the module (I've
never used "cvs watch add", "cvs watch remove", or "cvs watch off") and just
using "cvs ci", "cvs edit", and "cvs unedit".

Noel





[EMAIL PROTECTED] on 03/02/2000 11:41:37 AM

To:   [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:   [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject:  RE: cvs watch





       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





Reply via email to