From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup tarballs (was: Re: patching 2.6.16 with speakup-2.0)
Date: Mon, 1 May 2006 14:30:45 -0700 [thread overview]
Message-ID: <20060501213045.GA3277@localhost.localdomain> (raw)
In-Reply-To: <20060501211447.GA15652@lava-net.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Since they're ready for upload, I assume they work when they're
patched in, like the official tar releases do. In that case, mind
sharing the steps you took to create the tarball? I know I wouldn't be
the only one interested. Thanks.
Greg
On Mon, May 01, 2006 at 05:14:47PM -0400, Igor Gueths wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi all. I've checked out the latest CVS and created speakup-2.0-linux-2.6.16.tar.gz, and speakup-2.0-linux-2.6.16.tar.bz2. Should I upload those to /pub/incoming on linux-speakup.org?
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEVn4F7s9z/XlyUyARAokyAKDUZs1OJH2WZpTOQyspLTo8wxfx2wCgxy55
950l9/ijpgrACkZaZR3FVqY=
=6Eq/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
patching 2.6.16 with speakup-2.0 John Heim
` Gregory Nowak
` ace
` Gregory Nowak
` Steve Holmes
` Speakup tarballs (was: Re: patching 2.6.16 with speakup-2.0) Igor Gueths
` Gregory Nowak [this message]
` Igor Gueths
` Gregory Nowak
` Steve Holmes
` Igor Gueths
` Steve Holmes
` patching 2.6.16 with speakup-2.0 John Heim
` Lorenzo Taylor
` Steve Holmes
` Steve Holmes
` John Heim
` Kirk Reiser
` Steve Holmes
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=20060501213045.GA3277@localhost.localdomain \
--to=greg@romuald.net.eu.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).