This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Interesting words from gcc.info


>> > The words below were written by Richard Stallman, I believe:
>> >
>> > Reporting Bugs
>> > **************
>> >
>> >    Your bug reports play an essential role in making GCC reliable.
>> >
>> >    When you encounter a problem, the first thing to do is to see if it
>> > is already known.  *Note Trouble::.  If it isn't known, then you should
>> > report the problem.
>> >
>> >    Reporting a bug may help you by bringing a solution to your problem,
>> > or it may not.  (If it does not, look in the service directory; see
>> > *Note Service::.)  In any case, the principal function of a bug report
>> > is to help the entire community by making the next version of GCC work
>> > better.  Bug reports are your contribution to the maintenance of GCC.
>> >
>> >    Since the maintainers are very overloaded, we cannot respond to
every
>> > bug report.  However, if the bug has not been fixed, we are likely to
>> > send you a patch and ask you to tell us whether it works.
>> >
>> > Interesting philosophy.
>>
>> Any part in particular?  (I'm wondering what you're commenting on.)
>
>That's what I was thinking.  Just wait 'till he reads the GNU Manifesto ;-)

I was commenting on the general philosophy of bug reporting.  Few, if
any, of the principles outlined above are in evidence in this mailing
list.

cgf

<rofl>  No, they're not.  I see four things mentioned:
1.  See if the problem you have is already known (search archives, etc.).
2.  If it's not known, report it.
3.  The maintainers aren't bound to respond to your email.
4.  If it is in fact a bug, the maintainers will make an attempt to fix it
and send you the patch to see if it works.

This list is more like:
1.  Hey, is this a bug? (meanwhile, fourteen other people last week all said
"Hey, is this a bug?")
2.  The maintainers *are* bound to respond to your email -- "Hey moron, read
the FAQ, read the archives, and send us a patch!"

<bg>

Vince


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]