Till Maas wrote:
On Tue May 27 2008, Andrew Farris wrote:
Till Maas wrote:
Also it can be easily seen on a bug search results page. Maybe it could
be agreed on a special way to mention it in case it is not already
obvious, e.g. add the language in parenthesis after the package name,
e.g.
Review Request: foobarmatic (ruby) - some foo for bar
But language as a freeform random part of summary is not very clear either.
I did not suggest a freeform random part but a defined part of the subject,
e.g. in parentheses.
Review Request: foobarmatic c - some foo for C++ code documentation parsing
Review Request: foobarmatic written in c++ - makes ruby colored slippers
Review Request: foobarmatic perl - pythons on a plane
Review Request: foobarmatic (c) - some foo for C++ code documentation parsing
Review Request: foobarmatic (c++) - makes ruby colored slippers
Review Request: foobarmatic (perl) - pythons on a plane
Nevertheless getting everyone to conform to something that arbitrary is more
difficult than tagging a tracker bug.
--
Andrew Farris <lordmorgul@xxxxxxxxx> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
