From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: <speakup@braille.uwo.ca>
Subject: Re: Tuxtalk
Date: Sun, 10 Jun 2001 22:06:09 +0200 [thread overview]
Message-ID: <005001c0f1ea$33163ab0$0100a8c0@cybertsar> (raw)
In-Reply-To: <Pine.LNX.4.32.0106091043210.812-100000@data.home>
What will the existing Tuxtalk module add to the capabilities of Speakup,
compiled in the kernel? Does Speakup already communicate with this module?
Best regards,
Vic
----- Original Message -----
From: "Geoff Shang" <gshang@uq.net.au>
To: <speakup@braille.uwo.ca>
Sent: Saturday, June 09, 2001 2:45 AM
Subject: Re: Tuxtalk
> Hi:
>
> Tuxtalk such as it is can be obtained from the CVS repository.
>
> Server: linux-speakup.org
> User: anonymous
> Password: please
> Module: tuxtalk
>
> Kirk please correct this if it's wrong.
>
> I'm assuming you know how to use CVS, let me know if you don't.
>
> Geoff.
>
>
>
> _______________________________________________
> 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: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
Tuxtalk JONATHAN CREASY
` Tuxtalk Raul A. Gallegos
` Tuxtalk Geoff Shang
` Victor Tsaran [this message]
` Tuxtalk Terry D. Cudney
` Tuxtalk Geoff Shang
Tuxtalk JONATHAN CREASY
tuxtalker Saqib Shaikh
` tuxtalk Terry Cudney
exim slackware package Gregory Nowak
` tuxtalk randy turner
` tuxtalk Kirk Reiser
` tuxtalk randy turner
` tuxtalk randy turner
` tuxtalk Sergey Fleytin
` tuxtalk David Csercsics
tuxtalk Deedra Waters
` tuxtalk David Csercsics
` tuxtalk Alex Snow
` tuxtalk Lorenzo Prince
` tuxtalk Steve Holmes
` tuxtalk Steve Holmes
` tuxtalk Kirk Reiser
` tuxtalk Steve Holmes
TuxTalk ace
` TuxTalk Gregory Nowak
` TuxTalk ace
` TuxTalk Gregory Nowak
` TuxTalk ace
` TuxTalk Kirk Reiser
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='005001c0f1ea$33163ab0$0100a8c0@cybertsar' \
--to=tsar@sylaba.poznan.pl \
--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).