From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: speakup and intrepid 2.6.27.4 kernel patch?
Date: Wed, 24 Sep 2008 11:27:54 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.0809241125250.24589@localhost.localdomain> (raw)
In-Reply-To: <20080924084448.GB4527@implementation.bordeaux.inria.fr>
As the speakup fix did not go into the 2.6.27 kernel, would it be safe to
do the speakup patch and rebuild of the kernel the old way?
TIA, Willem
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Debianized 2.6.26 Kernel Erik Heil
` Samuel Thibault
` Willem van der Walt [this message]
` speakup and intrepid 2.6.27.4 kernel patch? Samuel Thibault
` Debianized 2.6.26 Kernel Erik Heil
` Samuel Thibault
` Erik Heil
` Samuel Thibault
` Erik Heil
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=Pine.LNX.4.64.0809241125250.24589@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--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).