From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Bugs Bugs Bugs & Unstablity
Date: Tue, 23 Jul 2002 18:53:14 -0400 [thread overview]
Message-ID: <3D3DDE5A.2080909@gentoo.org> (raw)
All I ever hear or read about is people complaining about bugs or
stability issues or an ebuild problem. Granted I'm not complaining about
this, this is good... we need to know this. But there is one thing
missing... I go to http://bugs.gentoo.org and sort through the bugs and
there are hardly any bug reports for the problems people say.
Here's a couple things I'd like to see our users do as far as bugs
1) Fill out bug reports @ http://bugs.gentoo.org
2) Provide us with all the necessary details... for example... if you
just tell me that libfoo's latest ebuild doesn't compile for you. That
is definetly not enough detail. Provide the FULL version including our
ebuild revision, such as libfoo-1.0.1-r1.ebuild is what we'd like to see.
3) You NEED to tell us which version compiler you are using.
4) You need to tell us your USE flags and your CFLAGS
5) Provide us with a copy and paste of the exact error message.
6) Any other data you feel might be revelant.
If you do all that more bugs will be fixed and they will hopefully be
fixed faster.
And if the person who sent me the patch against the latest version of
pcmcia-cs over IRC in a /query while I was gone is here.... please fill
out a bug report and lemme know what it fixes and include it. My battery
on the laptop ran out while I was gone.
In conclusion, you need to submit your bugs and concerns in a reliable
fashion so that they can be properly addressed... the only way to do
that is to fill out a bug report.
--
Doug Goldstein
Developer (Laptops, WiFi, GCC-3.1)
Gentoo Linux http://www.gentoo.org/~cardoe/
next reply other threads:[~2002-07-23 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 22:53 Doug Goldstein [this message]
2002-07-23 23:08 ` [gentoo-dev] Bugs Bugs Bugs & Unstablity Stefano Peluchetti
2002-07-24 7:16 ` Vitaly Kushneriuk
2002-07-24 8:13 ` Kim Nielsen
2002-07-24 11:47 ` Jean-Michel Smith
2002-07-24 18:31 ` Paul de Vrieze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D3DDE5A.2080909@gentoo.org \
--to=cardoe@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox