From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Trouble Compiling modules/kernel
Date: Wed, 7 Jan 2009 17:28:41 -0600 [thread overview]
Message-ID: <CCADD79751C34890BE12066E8E9C638C@CHIHUAHUAL1> (raw)
In-Reply-To: <20090107232327.GD4991@const.famille.thibault.fr>
Hi, I totally agree. No wonder lots of distributions don't have speakup if
the information on the linux speakup site was updated then probably speakup
could be back in versions of linux that it was in before and even more
versions that never had it. Can you quickly give me instructions on getting
the git version I have debian and have already done apt-get install git-core
so have git installed on my system. Why is the cvs version even still on
the site if it is no longer being maintained?
----- Original Message -----
From: "Samuel Thibault" <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, January 07, 2009 5:23 PM
Subject: Re: Trouble Compiling modules/kernel
Zachary Kline, le Wed 07 Jan 2009 12:35:01 -0800, a écrit :
> There are many detailed sets of instructions in the list archives on
> how to do this.
Could these find their way to http://linux-speakup.org ? It's a problem
that information there is mostly outdated.
Samuel
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Joe Kamphaus
` Zachary Kline
` Samuel Thibault
` Nick Gawronski [this message]
[not found] ` <0A98E1637487415A909D77F28CEBB13A@bouncy>
[not found] ` <44E48C85D8FD47EAA0C4A4D7C36CA1B8@chihuahuad1>
` Kerry Hoath
` Nick Gawronski
` Gregory Nowak
` Kerry Hoath
` Gregory Nowak
` Nick Gawronski
[not found] <mailman.1.1231434002.20588.speakup@braille.uwo.ca>
` Joe Kamphaus
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=CCADD79751C34890BE12066E8E9C638C@CHIHUAHUAL1 \
--to=nick@nickgawronski.com \
--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).