Eric Boutilier <Eric.Boutilier at Sun.COM> writes: > Mark Fenwick wrote: > > Hi Eric, > > > > Do you know if there is a bug catagory for the mercurial config ? > > > > Do you know who looks after issues with mercurial ? > > > > Recap: > > > > When changes are pushed from the gate to another gate, the update e-mail > > comes from the last person to upgate /ws/onnv-gate rather than the person > > who did the push! > > > > Thanks > > > > Mark > > I asked around and the feedback was that this should be discussed > on the scm-migration-dev list (copied), and that it's probably > related to how the Mercurial hooks are programmed to work.
It currently works like this: Notification mail is From: the author of the changeset (mapped to an address via the opensolaris database, sometimes badly). If you push greater than 10 changesets, this notification is coalesced into a single mail, however, due to the way that is done, it also loses information and, for want of a better phrase "looks wrong". I can't fix this, it runs on opensolaris.org. I couldn't even reasonably test a fix. It's also worth noting that any change in the behaviour described by the first paragraph would make onnv-notify less useful, at present. If, for whatever reason, a fix here is seen as pressing, and someone gives me sufficient detail as to what they'd rather happen. I'm willing to fix it, if someone else is willing to both test and install the changes on opensolaris.org -- Rich
