[Cvs-syncmail] [ cvs-syncmail-Patches-1021987 ] suppress certain branch checkin mails

[SourceForge.net <no...@so...>]

Patches item #1021987, was opened at 2004-09-03 14:12
Message generated for change (Comment added) made by fdrake
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450021&aid=1021987&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Skip Montanaro (montanaro)
Assigned to: Nobody/Anonymous (nobody)
Summary: suppress certain branch checkin mails

Initial Comment:
In our environment we have an unwritten policy that
most extensive new development occurs on development
branches, not on the trunk.  Aside from the trunk we
also have maintenance branches whose names follow a
consistent naming rule.

When development occurs over a longish period of time,
developers tend to merge from the trunk periodically so
as not to get too out-of-sync, then checkin the merge
results on the branch.  This can result in large
numbers of fairly worthless syncmail messages.

The attached patch allows you to specify a tag pattern
on the syncmail command line.  For example, all our
maintenance branches have names like snake_1_19_branch.
By giving

    -t 'snake[0-9_]+branch'

as an arg to syncmail, only checkins on the trunk or
such maintenance branches generate email output.
Merges from development branches to the trunk are seen
because all trunk checkins continue to generate email.

This certainly isn't for everyone.  I imagine it will
be most useful for small development groups with other
ways of keeping up-to-date with ongoing work in
development branches besides CVS.  For widespread open
source projects it probably doesn't make much sense.
It works for us because each development branch is the
responsibility of a single person and all developers
are within a few feet of each other.


----------------------------------------------------------------------

>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2004-10-06 22:18

Message:
Logged In: YES 
user_id=3066

I think this will be covered by the changes in the version
on the "new-config-branch" branch, but I'll leave it open
for now, since I've not reviewed that aspect of the code in
a while.

(The branch has other problems at the moment, though.)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450021&aid=1021987&group_id=47611