From: Daniel Egger <degger@fhm.edu>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org, Tux mailing list <tux-list@redhat.com>
Subject: Re: How to make Linux/Tux/Whatever better? (was Re: TUX development? Anyone?)
Date: 15 Feb 2002 20:11:54 +0100 [thread overview]
Message-ID: <1013800315.2244.18.camel@sonja> (raw)
In-Reply-To: <Pine.LNX.4.30.0202151956290.21207-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0202151956290.21207-100000@mustard.heime.net>
Am Fre, 2002-02-15 um 19.59 schrieb Roy Sigurd Karlsbakk:
> Is it only me?
> Can I please get *some* sort of feedback after submitting a bug report?
> I thought that was what made open-source projects better...
You don't get the point, do you?
You get what pay for and in this case it's zilch, zero, nada, nothing...
... No, wait, you have the source, that's more than nothing. Use it,
Luke!
When there's no developper interesting in fixing the bug you've found in
her/his sparetime you should consider buying some help or fix it
yourself instead of complaining.
--
Servus,
Daniel
next prev parent reply other threads:[~2002-02-15 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 13:21 TUX development? Anyone? Roy Sigurd Karlsbakk
2002-02-15 13:57 ` Arjan van de Ven
2002-02-15 18:32 ` Roy Sigurd Karlsbakk
2002-02-15 18:39 ` Rik van Riel
2002-02-15 18:44 ` Roy Sigurd Karlsbakk
2002-02-15 18:45 ` Arjan van de Ven
2002-02-15 18:59 ` How to make Linux/Tux/Whatever better? (was Re: TUX development? Anyone?) Roy Sigurd Karlsbakk
2002-02-15 19:11 ` Daniel Egger [this message]
2002-02-19 18:23 ` Ben Greear
2002-02-15 19:31 ` Rik van Riel
2002-02-16 5:42 ` Michael E Brown
2002-02-16 17:48 ` Horst von Brand
2002-02-15 22:52 ` TUX development? Anyone? Ingo Molnar
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=1013800315.2244.18.camel@sonja \
--to=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=tux-list@redhat.com \
/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