On Tue, 2008-12-09 at 22:28 +0100, Thorsten Schöning wrote: > > What is the overhead you are referring to ? > > I meant I didn't want to file a bug and commit the update against that > filed bug just to get mail notifications. For this way to work I would > need all customers in our Bugzilla but we don't work that way, yet.
Yet. Hmm... It sounds as if we need a new policy that will send additional emails, not just notify bug reporters, owners, etc, when commits occur on specific paths. > > It seems that you need to implement on the Scmbug daemon the logic for a > > policy of sending different emails based on which paths a changeset is > > applied. > > Do you think setting a svn-property on a path where mails should be > send to XY would be a way to go? I thought of something like the > bugtraq-properties provided by some svn-tools, like TortoiseSVN. This > way I could configure everything via repository and I thought that > SCMBug already gets the path a commit was done in, therefore it > shouldn't be too hard to get the properties if they are set > recursively. I don't like the svn-property idea. CVS and Git don't have svn-properties. The solution should be, and can be, general. By implementing a new policy. How does this sound ? > Any ideas on how to achieve such mail notifications without to much > coding? Any trick one is aware of? I'm afraid we can't use what Scmbug offers already to implement what you are asking for (unless you want customers to be in Bugzilla as you already discovered).
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
