7:34 a.m.
Here are a small collection of subject lines of emails sent
automatically to me by various Fedora systems in the past few days:
Subject: upgradepath PASSED for FEDORA-2015-850e89be8b
Subject: [Fedora Update] [comment] auto-buildrequires-1.2-1.fc23
Subject: rjones's libguestfs-1.33.1-2.fc24 completed
Subject: rpmlint PASSED for libguestfs-1.33.1-2.fc24
Subject: Broken dependencies: libguestfs
Subject: ABRT report for package gnome-boxes has reached 10 occurrences
Subject: [Bug 1269975] svirt very occasionally prevents parallel libvirt [..]
Subject: Fedora 'packager' sponsor needed for suanand
Subject: sailer's mingw-sqlite-3.10.1.0-1.fc24 failed to build
Subject: libguestfs's builds are back to normal in f24
Subject: dchen pushed to ocaml-lwt (el6). "New upstream version 2.2.0."
The only consistent thing is there's nothing consistent about them :-/
I'd like to propose a very lightweight "standard" for subject lines of
emails.
(1) The first word should be the package name which the email
concerns. If the email is not about a package, but about a person,
then the first word should be the FAS username of that person.
(2) The second word should be the status, reflecting what the reader
needs to know or do, for example "succeeded", "failed",
"submitted".
That's it!
The above subject lines might become (chopped to 72 characters to
simulate what you might see in a text-based email reader):
Subject: auto-buildrequires passed: upgradepath FEDORA-2015-850e89be8b
Subject: auto-buildrequires submitted: auto-buildrequires-1.2-1.fc23
Subject: libguestfs completed: rjones's libguestfs-1.33.1-2.fc24 build c
Subject: libguestfs passed: rpmlint libguestfs-1.33.1-2.fc24
Subject: libguestfs failed: Broken dependencies found in package libgues
Subject: gnome-boxes failed: ABRT report for package gnome-boxes has rea
Subject: selinux-policy comment: [Bug 1269975] svirt very occasionally p
Subject: suanand requested: Fedora 'packager' sponsor needed for suanand
Subject: mingw-sqlite failed: sailer's mingw-sqlite-3.10.1.0-1.fc24 fail
Subject: libguestfs passed: libguestfs's builds are back to normal in f2
Subject: ocaml-lwt pushed: dchen pushed to ocaml-lwt (el6). "New upstre
Maybe you have some better ideas?
A related topic is headers, which could be used for filtering.
Various systems add headers -- see examples below -- but again there's
not much consistency and the headers aren't particularly useful for
filtering.
Rich.
X-Fedmsg-Topic: org.fedoraproject.prod.taskotron.result.new
X-Fedmsg-Category: taskotron
X-Fedmsg-Package: libguestfs
X-Bodhi-Update-Builds: auto-buildrequires-1.2-1.fc23
X-Bodhi-Update-Pushed: True
X-Bodhi-Update-Type: enhancement
X-Bodhi-Update-Release: F23
X-Bodhi-Update-Status: testing
X-Bodhi-Update-Request: stable
X-Bodhi-Update-Submitter: rjones
X-Bodhi-Update-Title: auto-buildrequires-1.2-1.fc23
X-Bodhi: fedoraproject.org
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
7:43 a.m.
Am 16.01.2016 um 14:34 schrieb Richard W.M. Jones:
Here are a small collection of subject lines of emails sent
automatically to me by various Fedora systems in the past few days:
Subject: upgradepath PASSED for FEDORA-2015-850e89be8b
Subject: [Fedora Update] [comment] auto-buildrequires-1.2-1.fc23
Subject: rjones's libguestfs-1.33.1-2.fc24 completed
Subject: rpmlint PASSED for libguestfs-1.33.1-2.fc24
Subject: Broken dependencies: libguestfs
Subject: ABRT report for package gnome-boxes has reached 10 occurrences
Subject: [Bug 1269975] svirt very occasionally prevents parallel libvirt [..]
Subject: Fedora 'packager' sponsor needed for suanand
Subject: sailer's mingw-sqlite-3.10.1.0-1.fc24 failed to build
Subject: libguestfs's builds are back to normal in f24
Subject: dchen pushed to ocaml-lwt (el6). "New upstream version 2.2.0."
The only consistent thing is there's nothing consistent about them :-/
I'd like to propose a very lightweight "standard" for subject lines of
emails.
(1) The first word should be the package name which the email
concerns
in context of that the subjects below needs to be fixed listing all
subpackages and exceed TWO KILOBYTE subject header because place the
package in front would prevent to see anything else (in case of other
packages not exceeding 2048 byte but have subpackages too)
Jan 7 05:23:03 mail-gw postfix/cleanup[2859]: 3pbZDQ6RR5z2B: reject:
header Subject: [Fedora Update] [CRITPATH] [comment]
kf5-kdoctools-5.18.0-1.fc23 kf5-kdbusaddons-5.18.0-1.fc23
kf5-kio-5.18.0-1.fc23 kf5-kjsembed-5.18.0-1.fc23
kf5-ktextwidgets-5.18.0-1.fc23 kf5-kidletime-5. from
bastion01.fedoraproject.org[209.132.181.2];
from=<updates(a)fedoraproject.org> to=<h.reindl(a)thelounge.net> proto=ESMTP
helo=<bastion.fedoraproject.org>: 5.7.1 Administrative Prohibition
(Subject-Header Too Long)
1:54 p.m.
On Sat, 16 Jan 2016 13:34:12 +0000
"Richard W.M. Jones" <rjones(a)redhat.com> wrote:
Here are a small collection of subject lines of emails sent
automatically to me by various Fedora systems in the past few days:
Subject: upgradepath PASSED for FEDORA-2015-850e89be8b
Subject: [Fedora Update] [comment] auto-buildrequires-1.2-1.fc23
Subject: rjones's libguestfs-1.33.1-2.fc24 completed
Subject: rpmlint PASSED for libguestfs-1.33.1-2.fc24
Subject: Broken dependencies: libguestfs
Subject: ABRT report for package gnome-boxes has reached 10
occurrences Subject: [Bug 1269975] svirt very occasionally prevents
parallel libvirt [..] Subject: Fedora 'packager' sponsor needed for
suanand Subject: sailer's mingw-sqlite-3.10.1.0-1.fc24 failed to build
Subject: libguestfs's builds are back to normal in f24
Subject: dchen pushed to ocaml-lwt (el6). "New upstream version
2.2.0."
The only consistent thing is there's nothing consistent about them :-/
I'd like to propose a very lightweight "standard" for subject lines of
emails.
...snip...
I think this is a great idea!
I'll bring up the subject on the infrastructure list and see what folks
there think of it.
kevin
1:48 a.m.
On Sat, 2016-01-16 at 12:54 -0700, Kevin Fenzi wrote:
On Sat, 16 Jan 2016 13:34:12 +0000
"Richard W.M. Jones" <rjones(a)redhat.com> wrote:
> Here are a small collection of subject lines of emails sent
> automatically to me by various Fedora systems in the past few days:
>
> Subject: upgradepath PASSED for FEDORA-2015-850e89be8b
> Subject: [Fedora Update] [comment] auto-buildrequires-1.2-1.fc23
> Subject: rjones's libguestfs-1.33.1-2.fc24 completed
> Subject: rpmlint PASSED for libguestfs-1.33.1-2.fc24
> Subject: Broken dependencies: libguestfs
> Subject: ABRT report for package gnome-boxes has reached 10
> occurrences Subject: [Bug 1269975] svirt very occasionally prevents
> parallel libvirt [..] Subject: Fedora 'packager' sponsor needed for
> suanand Subject: sailer's mingw-sqlite-3.10.1.0-1.fc24 failed to build
> Subject: libguestfs's builds are back to normal in f24
> Subject: dchen pushed to ocaml-lwt (el6). "New upstream version
> 2.2.0."
>
> The only consistent thing is there's nothing consistent about them :-/
>
> I'd like to propose a very lightweight "standard" for subject lines
of
> emails.
...snip...
I think this is a great idea!
I'll bring up the subject on the infrastructure list and see what folks
there think of it.
I'm happy to take requests for the check-compose emails, if a common
scheme is decided.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
11:29 a.m.
On 16/01/16 13:34 +0000, Richard W.M. Jones wrote:
Here are a small collection of subject lines of emails sent
automatically to me by various Fedora systems in the past few days:
Subject: upgradepath PASSED for FEDORA-2015-850e89be8b
Subject: [Fedora Update] [comment] auto-buildrequires-1.2-1.fc23
Subject: rjones's libguestfs-1.33.1-2.fc24 completed
Subject: rpmlint PASSED for libguestfs-1.33.1-2.fc24
Subject: Broken dependencies: libguestfs
Subject: ABRT report for package gnome-boxes has reached 10 occurrences
Subject: [Bug 1269975] svirt very occasionally prevents parallel libvirt [..]
Subject: Fedora 'packager' sponsor needed for suanand
Subject: sailer's mingw-sqlite-3.10.1.0-1.fc24 failed to build
Subject: libguestfs's builds are back to normal in f24
Subject: dchen pushed to ocaml-lwt (el6). "New upstream version 2.2.0."
The only consistent thing is there's nothing consistent about them :-/
I've been thinking about complaining about the very same thing!
(2) The second word should be the status, reflecting what the reader
needs to know or do, for example "succeeded", "failed",
"submitted".
Yes! Some scratch builds have a really long header and the
"completed" or "failed" is not visible even with far more than 72
characters shown.
Maybe you have some better ideas?
LGTM.
A related topic is headers, which could be used for filtering.
Various systems add headers -- see examples below -- but again there's
not much consistency and the headers aren't particularly useful for
filtering.
Yes again. It would be great if the headers were more useful.
9:27 a.m.
On Sat, Jan 16, 2016 at 01:34:12PM +0000, Richard W.M. Jones wrote:
A related topic is headers, which could be used for filtering.
Various systems add headers -- see examples below -- but again there's
not much consistency and the headers aren't particularly useful for
filtering.
A standard header indicating just that the message is automatically
generated would also be helpful, for a) putting them in a separate
folder and b) filtering them out of analytics.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9:44 a.m.
Am 18.01.2016 um 16:27 schrieb Matthew Miller:
On Sat, Jan 16, 2016 at 01:34:12PM +0000, Richard W.M. Jones wrote:
> A related topic is headers, which could be used for filtering.
> Various systems add headers -- see examples below -- but again there's
> not much consistency and the headers aren't particularly useful for
> filtering.
A standard header indicating just that the message is automatically
generated would also be helpful, for a) putting them in a separate
folder and b) filtering them out of analytics
the redhat-bugzilla does that after a bugreport from me long ago and the
main purpose of them is to avoid autorepsonders (all sane autorepsonders
supress replies if that headers are present, not only but also for
loop-protection)
Precedence: bulk
Auto-Submitted: auto-generated
3081
days inactive
3083
days old
6 comments
6 participants
participants (6)
-
Adam Williamson -
Jonathan Wakely -
Kevin Fenzi -
Matthew Miller -
Reindl Harald -
Richard W.M. Jones