Please "attach" files to bugzilla, instead of pasting into a massive comment
jpearson42 at wowway.com
Thu Mar 9 15:00:06 UTC 2006
On Thursday 09 March 2006 2:08 am, Mike A. Harris wrote:
> Warning: Frustration rant follows.
> More and more over time, I am noticing a tendency of bug reporters
> adding log files, config files and other large files to bug reports
> by cutting and pasting these massive files into the comment box,
> instead of attaching them as proper bugzilla file attachements.
> As a developer, this is very irritating because it makes the bug
> report incredibly long to view....
I have been following this mail list and trying to help with testing since I
now have some time and resources available. In more than a year's time, I
have filed, perhaps, 2 bug reports. From my perspective, it is hard to know
what information is required, necessary, useful. If I have asked on the
list, and sometimes been answered, sometimes not. While I use computers, an
occasional bash script is the depth of my programming ability on Linux. When
trying to specify hardware, I am not sure if there are a set of diagnostic
commands to run, or if I need a screwdriver and a magnifying glass to
identify part numbers and revision levels.
> This is very very irritating. Please help us (developers) to help
> you (bug reporters/testers), by using bugzilla properly, and
> thinking about what it is like to be on the receiving end of 500
> bug reports and get 30 like this.
A style guide, a one page document of what you need for system identification,
a set of suggested queries to obtain the information, and a suggested
placement of the information would be very useful.
My desk is littered with post-it notes, but I don't know if lspci -v
or lspci -vv is the preferred choice.
> Feature request filed:
> Mike A. Harris * Open Source Advocate * http://mharris.ca
> Proud Canadian.
More information about the fedora-test-list