Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
He who wonders discovers that this in itself is wonder.
-- M.C. Escher
On Wed, 15 Jul 1998, Raul Miller wrote:
> Dale Scheetz <email@example.com> writes:
> > > Well, I disagree with this point of view. Yes, Debian wishes to support
> > > newcomers to Linux. That is why we have debian-user. We have a
> > > responsibility to those new users to "train" them to be "free" users.
> > > They can only do that if they become familiar with the ins and outs of the
> > > "Debian Way".
> John Goerzen <firstname.lastname@example.org> wrote:
> > But by actually submitting a bug report in the first place, they're
> > already helping. The maintainer can either fix it or open a dialogue
> > up with the submitter if more information is needed.
> Slow down folks. [Er... except on getting hamm released.]
> Dale is talking from the viewpoint of being libc maintainer. John
> is talking about the application view of the system.
Just from the point of view of a typical user, eg, me....
just doing a quick scan of the debian-user archives doesn't
take all that long. They're very up-to-date, usually just a
day or so behind. Browsing the archives with navigator presents
a nice threaded layout, easily scanned in a few minutes.
Besides, you might actually learn something in spite of yourself.
And if you find an answer, you'll conserve Net bandwidth + make
it easier for the next user to perhaps find HIS answer in the
> 100 emails/per day posted to debian-user.
Unsubscribe? mail -s unsubscribe email@example.com < /dev/null