On Wed, 07 Aug 2013 10:46:04 +0200 Kacper Kowalik <xarthis...@gentoo.org> wrote:
> Not so hypothetical situation: someone files a bug: "Fancy KDE mail > program fails with my gcc", you fix it and live happily ever after. > How on earth am I supposed to find it when porting/stabilizing newer > version of gcc? > I expect (as many others) something similar to "=kde-base/kmail-4.8.10 > fails to build with gcc-4.8" We usually take it a step further, putting the actual error there; if the maintainer reads the error, it will be clear it failed to build: "=kde-base/kmail-4.8.10 with GCC 4.8 - File:Line:Char: Error: Reason" > I deeply respect the work of people who fix bugzilla subjects to > conform to "atom: issue" format. It saves me a great deal of time. Thank you. As a side note, I believe the separator for this format isn't defined; I see people as well as myself commonly use " - " as a separator, so I'm not sure where the ": " separator came from and don't see it as something to conform to (neither do I see " - " as such). This mail isn't meant to start a bike shed, but I just don't want either format to be seen as the definitive format; unless of course, there has been a prior consensus on what the separator should be. If there has been a prior discussion, and this is why I reply, I would like to know. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
