From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: patching 2.6.16 with speakup-2.0
Date: Mon, 1 May 2006 13:38:13 -0700 [thread overview]
Message-ID: <20060501203813.GA2188@localhost.localdomain> (raw)
In-Reply-To: <20060501210611.GB3465@amelia.voyager.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, May 01, 2006 at 04:06:11PM -0500, ace wrote:
> What is the point of even having a tarball release if it is broken?
The point is that when the tarball was released, it worked with the
then currently newest kernel version, so it wasn't broken.
> Just curious. It seems as though there should be a tarball release with
> every major kernel release (when things usually seem to break) or just
> stop producing tarballs.
>
I'm sure that Kirk would be more then happy to let you checkout cvs
into a tarball whenever a new kernel comes out, and make that tarball
available for the rest of us on ftp.linux-speakup.org/pub/speakup/.
Greg
- --
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)
iD8DBQFEVnG17s9z/XlyUyARAtE8AJ9RhIRZkqDdznjTeG7yUblV4hKgKQCgyVTl
/JW9oi7Ua15qog7DVdGiEpE=
=HKFi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
John Heim
` Gregory Nowak
` ace
` Gregory Nowak [this message]
` Steve Holmes
` Speakup tarballs (was: Re: patching 2.6.16 with speakup-2.0) Igor Gueths
` Gregory Nowak
` 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=20060501203813.GA2188@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).