Hi James, On Fri, 2009-01-30 at 15:34 -0600, James Webb wrote: > To all, > > > I was going through the archives and buglist and found there is a bug for > possibly using the native bugtracker's email ability to send emails. I wanted > to know what happened to that idea?
You are referring to two different things: 1) Use the native bugtracker's email ability to send emails. http://bugzilla.mkgnu.net/show_bug.cgi?id=784 2) Actually FOLLOW the bugtracker's email process when a commit happens or a tag is applied. http://bugzilla.mkgnu.net/show_bug.cgi?id=832 If we skipped (1), all would still be well, because... we still have an ability to send emails. We haven't implemented (2) yet. A patch for (2) was developed, but it has not been merged yet. > What the real issue is... I am not sure what the real issue you are describing is. > I have a simple hook setup to email all staff when a commit happens. But > what I want is a second email to be sent for bug updates such > as "[productname] [bug 1000]... " but I don't want > "[productname] [bug NONE]... ". First, these emails are sent by Scmbug, not the bug-tracker. Thus, the discussion of (1) and (2) are irrelevant here. Second, why ? Does "[bug NONE]" bother you ? What is the real issue ? I believe "[bug NONE]" will be sent if you are using CVS and you are applying a tag. This is configurable. You can choose to NOT send emails when tagging by setting mail_on_label to 0 in glue.conf. > Obviously you only get an email from Bugzilla when you edit a real bug; > and, it only goes out to the ones assigned to the bug or who placed the bug. ..? I hope this helps somewhat... ?
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
