![](https://seccdn.libravatar.org/avatar/cb2aaf49f775c94d4056311eef22be7b.jpg?s=120&d=mm&r=g)
Am 06.12.2013 22:55, schrieb Christian Boltz:
Hello,
Am Freitag, 6. Dezember 2013 schrieb Stephan Kulow:
On 06.12.2013 13:59, Robert Schweikert wrote:
be great to have the project in the subject. For those that are project maintainers in multiple projects I think that is useful.
Requests can have several target projects. Just as they can several types. I add all actions and their targets in the mail headers though, but I don't want anything action specific in the subject, because it's just not logic.
Nevertheless, I'd guess most requests are about one package and one target - and for those it would be very helpful to have a meaningful subject with target project and package.
If a SR includes multiple packages (in the same target project), only add the target project to the subject.
And in case the SR delivers to 20 packages in 10 projects - well, then I'm ok with excluding them from the subject ;-)
An even better alternative would be to include only the first target, and prefix it with "10 targets, for example $first_target".
TL;DR summary:
"Subject: Request 123456: Review wanted" is about as helpful as "Subject: HELP !!!!!!111!!!" in a mailinglist ;-)
Then again, "Request 123456 (10 targets for example devel:languages:ruby:extensions/rubygem-activerecord-3_2), review wanted" is quite a long 'summary' :) The summary should "indicate the nature of the mail", not give away its content, but yeah, I agree that optimizing for the normal case of one target is feasible. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org