Mike Kupfer wrote:
I had 5 bounce messages in my inbox this morning from what looks like an
initial load of a crypto repository. All of the bounces were due to
(reason: 550 <[EMAIL PROTECTED]>: Recipient address rejected: User unknown
in local recipient table)
Perhaps the notification messages should contain an Errors-to: header?
It seems like the owner of the repo should get notified. And for an
initial load, errors should definitely not go to the people who did the
putbacks.
mike
I'll look into adding this; I was unaware of the Errors-to header
before, thanks for letting me know.
One other thing we probably need to figure out is whether we want to
define a relationship between parent/child repositories for
notifications. Ex:
onnv/onnv-gate & scm-migration/onnv-scm
I want notifications for real/project putbacks to scm-migration/onnv-scm
sent, but I don't want notifications for changesets pulled from
onnv/onnv-gate.
I need to look into whether or not the incoming/pretxnchangegroup hooks
we're using now have the ability to differentiate between a push and a
pull. If so, then it'd be nice if we could setup some server-side
triggered method of telling scm-migration/onnv-scm to pull from
onnv-gate (and thus avoid notifications), while leaving notifications
for changesets pushed by committers/project-members.
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
[email protected]
