After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 89960 - changed-by in mail headers
changed-by in mail headers
Status: RESOLVED FIXED
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: email
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks: 60186
 
 
Reported: 2002-08-05 20:08 UTC by Owen Taylor
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Owen Taylor 2002-08-05 20:08:15 UTC
It would be really useful if there was an X-Bugzilla-Changed-By:
line in the headers.

I receive most of the mail from bugs I change via the gtk-bugs@gtk.org
"maintainer alias", so the bugzilla preference not to send mail
to me on bugs I change doesn't do any good. I'd like to be able
to filter these messages out via procmail.
Comment 1 David Fallon 2002-08-05 20:29:37 UTC
I'm virtually certain this is fixed when we upgrade, but if it isn't,
I'll make sure to add it.
Comment 2 Luis Villa 2002-08-05 21:09:44 UTC
I'm pretty sure it's not unless we patch it. It's pretty trivial to
add, though.
Comment 3 James Henstridge 2004-03-26 09:41:15 UTC
A better way to set this up (which is quite easy to do with 2.16) would be to
log into bugzilla as gtk-bugs@gtk.org, and uncheck all the mail options in the
preferences.

Then log in as yourself again, and on the mail preferences add gtk-bugs@gtk.org
to the "users to watch" entry field (all the other people on the
gtk-bugs@gtk.org alias would have to do this too).

Now whenever a bug changes that would have caused a mail to be sent to
gtk-bugs@gtk.org, it will be sent to the accounts watching the that user.  This
way the "only send mail for other people's changes" option will be able to do
its job.

The other benefit is that users can add and remove themselves from GTK bug spam
via the web interface by themselves.
Comment 4 Luis Villa 2004-03-26 22:05:47 UTC
I've added the X-Bugzilla-Reasons header, which has some useful information as
to why you're getting a bug. I hope that's sufficient. 

Otherwise, as soon as halloween/mail-list syncing work, I'm going to urge
everyone to do as James has been pushing for some years now. He's right, it is
the way to go, and we can dump one more part of halloween, which will be nice.
[Hopefully when XML-RPC gets going, we can point bug-buddy at that, and then the
whole thing can go away :)
Comment 5 Luis Villa 2004-03-26 22:22:16 UTC
Hrm. So, looking at the Reasons header a bit more, I don't think it solves the
problem. That said, I'm going to close the bug anyway- fixing this the way you
want, Owen, would require more hacking, and it's going to be fixed anyway when
we move everyone away from the 'real' maint lists to a more alias-based
approach, which should be 'as soon as we can unsubscribe everyone from the
current lists.' Hope that's OK, Owen- please reopen if not.