From: Deedra Waters <dmwaters@gentoo.org>
To: gentoo-accessibility@lists.gentoo.org
Subject: [gentoo-accessibility] brltty
Date: Sun, 7 Mar 2004 11:35:56 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.58.0403071131080.8641@simba> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi guys!
I'm looking for volonteers who can test a new brltty ebuild. I'm hoping
that it will end up in portage some time today, but we'll see. Mainly
right now, I'm interested in finding people who can test this, and make
sure it does everything it's supposed to. I don't have the equipment to
test it, so this one is out of my hands.
Anyway, if any you can test it, or know someone who uses gentoo, and wants
to test it I'd appreciate it.
- --
Gentoo Linux: dmwaters@gentoo.org,
http://www.gentoo.org
Freenode staff member: dmwaters@freenode.net , http://www.freenode.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAS12CU5AGPOTGNc8RAlzLAJ9hlh72G750l94z7Lhd8iIOgSX0jwCfTFNQ
W0ZA5vM0SGynyi/PeBCsakU=
=kYeG
-----END PGP SIGNATURE-----
--
gentoo-accessibility@gentoo.org mailing list
next reply other threads:[~2004-03-07 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 17:35 Deedra Waters [this message]
2004-03-07 21:57 ` [gentoo-accessibility] brltty Nick Van Vlaenderen
2004-03-07 22:04 ` Deedra Waters
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 20:32 Deedra Waters
2007-03-06 0:09 [gentoo-accessibility] Brltty Zachary Kline
2007-03-19 17:12 [gentoo-accessibility] BRLTTY Zachary Kline
2007-03-19 21:45 ` Samuel Thibault
2007-03-19 22:10 ` Seemant Kulleen
2007-03-19 23:08 ` Zachary Kline
2007-03-20 3:25 ` William Hubbs
2007-03-20 3:26 ` Zachary Kline
2007-03-29 2:30 [gentoo-accessibility] brltty William Hubbs
2011-04-15 18:24 mattias
2011-04-15 23:33 ` William Hubbs
2011-04-16 9:27 ` mattias
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.58.0403071131080.8641@simba \
--to=dmwaters@gentoo.org \
--cc=gentoo-accessibility@lists.gentoo.org \
/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