Re: How to stop the originator of PRs from getting status mail

[Steffen Opel]

On Oct 25 Mark (Mark Schlegel) wrote:

note that I'm using GNATS 4.0 only and haven't used the 3.111 version 
you mentioned in your previous mail regarding this.

> What is entailed in stopping the submitter/originator of PRs from
> getting email upon each change of state to a PRs.

I think you got most to all of this right already in your own explanation 
in your previous mail, but just to get on the same track here, I'd say the 
submitter (ID) is something different than the originator, the GNATS terms 
may be a bit confusing sometimes since the originator 'submits' the PR:

- the originator is the individual who submitted the PR in first place
- each such originator may be associated with a submitter ID (!)
- each such ID may in turn be associated with a contact and a notification 
list

Think of this in terms of customer relationships:

You assign a customer (eg.g company A) a submitter ID; now every time 
a PR comes in with this submitter ID, whoever may have originated it, 
the address listed in the contact field of the submitters file will be 
notified of the incident and all further activities with this PR, as well 
as all addresses listed in the notification list.  The originator of the PR 
will only get an acknowlegment for the initial PR submission (if this feature 
is enabled), but not for subsequent PR activities.

> Do you just have to make the submitter file entry for
> that originator such that
> the 'contact' and 'notify-others' entries are 
> empty or should PRs be put in under the unknown
> submitter?

You should indeed only need to empty the fields, the 'unknown' submitter is 
something different as outlined above.  Since you already figured this 
right in your previous mail (the submitter entry you originally found seems 
to be faulty) I'm wondering why it didn't seem to work out?  
Or haven't you tested it this way?

Ciao,
Steffen


PS:  GNATS 4.0 allows much more finegrained control over the mail formats 
and addressees of the subsequent PR activities.  But then, it's not released 
yet and the maintainers are somewhat quiet at the moment ;-)