On Mon, 2013-09-16 at 10:58 +0200, Pierre-Yves Chibon wrote: > On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote: > > On Fri, Sep 13, 2013 at 10:38:41AM -0600, Kevin Fenzi wrote: > > > On Fri, 13 Sep 2013 17:35:20 +0200 > > > Jakub Filak <jfilak@xxxxxxxxxx> wrote: > > > > a bugzilla ticket [1] requiring a better Bugzilla summary field text > > > > produced by abrt has been filed. Before I start changing the bug > > > > summary format I'd like to do a little survey: > > > > > > > > What would you like see in the bug summaries produced by abrt? > > > > > > I actually disagree with the reporter of the bug. > > > > > > I prefer to have the component name in the subject of the bug. It's > > > true that you can look this up by going to the bug on the web and that > > > it's in the initial email, but after that the context of update emails > > > is not there, so it's harder for me to know _which_ of the many abrt > > > bugs this is. > > > > Please, fix/improve your email client UI. All bugzilla emails > > contain all necessary information in email header: > > Because opening email headers is indeed so convenient. > > > for example: > > > > X-Bugzilla-Reporter: > > X-Bugzilla-URL: https://bugzilla.redhat.com/ > > > > > > For example if you use mutt then all you need is to add > > > > unignore X-Bugzilla-Product X-Bugzilla-Component > > This is nice and handy, but I actually don't know many client offering this > opeiton. > /me gonna add this option to his muttrc (lucky that I do use mutt here and > there). Mutt you pointed it out, evolution seems to also support it: Edit -> Preferences -> Mail Preferences -> Headers Don't know about claws-mail but that's already more client than I thought :) Still feels hacky to me (and I would prefer the topic as proposed by Kevin) but ok, that's one option. Pierre -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
