From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: kernel pre-emption and software speech
Date: Thu, 5 Oct 2006 08:58:36 +0200 [thread overview]
Message-ID: <20061005065836.GB3185@implementation> (raw)
In-Reply-To: <cone.1159998431.363695.4776.0@layla>
Hi,
Michael Whapples, le Wed 04 Oct 2006 22:47:11 +0100, a écrit :
> In some cases we have to accept less than perfect code. By this I mean that
> it may function correctly with out no problems, but may need tidying up and
> other techniques may be more effecient, but if it is the only software that
> offers those functions then you should accept for what it gives, unless you
> are prepared to sort it out. Just leaving it definitely doesn't resolve the
> issues.
I'm sorry, but that's not how things work with Linux. The Reiser4 code
has been waiting for a long time for instance, and won't be merged
unless the required cleaning up happens.
> The other thing is that speakup seems to be good enough for some distros to
> include speakup in the default kernel and some others have it as an
> optional kernel but still in the main distro, and are they less stable than
> others? (these include slackware, gentoo, grml). I always found it strange
> that Redhat said how good speakup is, but never had it included on the main
> distro media.
The problem is not a stability problem, but a code correctness / style
/ ... You may have code that works, but if it is unmaintainable, some
day it won't work any more.
Samuel
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
Joshua Lambert
` Samuel Thibault
` Henrik Nilsen Omma
` Justin Ekis
` Samuel Thibault
` Henrik Nilsen Omma
` Kirk Reiser
` Steve Holmes
` Henrik Nilsen Omma
` John Heim
` Michael Whapples
` Gregory Nowak
` Samuel Thibault [this message]
` Samuel Thibault
` Michael Whapples
` Samuel Thibault
` John Heim
Samuel Thibault
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=20061005065836.GB3185@implementation \
--to=samuel.thibault@ens-lyon.org \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).