[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Notifications

From: Paul Van Delst
Subject: Re: CVS Notifications
Date: Thu, 18 Aug 2005 10:43:40 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.7.8-

S I wrote:
Hi All

I tried to do this couple of months ago but the requestors of it changed their mind, so I never got around to it. I've read the confusing manuals and examples in how to set up CVS Notifications. As the Admin and Build Engineer I want to be able to receive an email on only the committed files.

In CVSROOT on the server side:

1. In the notify file, I uncommented # ALL mail %s -s "CVS notification"

2. Created users file with my email address in it only and ran CVS add & commit.

3. In checkoutlist file, added, users Unable to checkout 'users' file in CVSROOT, to make it aware of users.

But the downside is that developers or me now have to run cvs watch & edit on the client side!

How can I set myself up to receive an email notification of only committed changes? I'm confused.

Don't you just have to do a
  cvs watch add -a commit
after a
  cvs watch on
in your working tree that you want to watch? You only have to do it once (doing it by directory should mean that any future added files are also watched by default.... at least, according to the docs). This should only notify you about commits, and not edits or unedits.

I set this up for a bunch of guys the other day when I did the initial checkout of the repository onto their local boxes. After the "checkout", I did a "watch on" and "watch add" at the working tree root. Now if they don't want to watch particular files or directories (and be possibly inundated with notification emails), they can turn it off themselves for particular files and/or directory trees at their leisure.

However, they still need to run "cvs edit" before they can edit their working copies that are being watched, but once they develop the habit it's not that big of a deal, right?



Paul van Delst

reply via email to

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