FS#13231 - [PATCH] (rc-script for var-run) laptop-mode-tools
Attached to Project:
Arch Linux
Opened by Gerardo Exequiel Pozzi (djgera) - Thursday, 12 February 2009, 07:53 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 21:41 GMT
Opened by Gerardo Exequiel Pozzi (djgera) - Thursday, 12 February 2009, 07:53 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 21:41 GMT
|
Details
Please read details in this mail:
http://www.archlinux.org/pipermail/arch-general/2009-February/003564.html |
This task depends upon
Heres the latest entry: http://phraktured.net/how-not-to-report-a-bug.html
from which quoting "Describe your bug via links to other things
The worst bug reports I see are of the following form: Subject: Bug with foobar I have the bug described here: http://some.bullshit.link
Why is this bad? Well, for one, I now have to follow yet-another-link to read, close that tab, remember what was written, and then read the rest of the bug report. Secondly, the links are usually forum posts, blog posts, or mailing list archives which never have the full information. I now need to read through 30 forum posts, stripping out the noise; or go through 5-10 back links for mailing list history; or even read comments on a blog to find out details of a bug report. A LINK IS NOT A BUG REPORT, IT IS A LINK" :)
But in this case i interpreted this as a """multiple feature request""". Then I published each patch separately, referring to the central theme, to be allocated to each maintainer.
But well, for the next take other precautions, when post multiple patches.
Again sorry.
In later time i will create better FR to join all series of this FR:
FS#13204FS#13211FS#13225FS#13226FS#13227FS#13228FS#13229FS#13230FS#13231FS#13232FS#13233FS#13234FS#13235