Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-accessibility
Navigation:
Lists: gentoo-accessibility: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-accessibility@g.o
From: Jeremy Huddleston <jeremy@...>
Subject: Re: 2.6 kernel and Speakup.
Date: Thu, 13 May 2004 11:07:26 -0700
Deedra, what gentoo-dev-kernel version do you have installed?  I can
make you a patch between the two and you can just hand apply it and
'emerge --inject' it.

--Jeremy

On Thu, 2004-05-13 at 05:29, Deedra Waters wrote:
> I've seen that. I need to talk to the person who is doing the 2.6 kernel source packages. I'm still waiting to hear back from him.  (and trying to figure out how I'm going to download a giant kernel tarball on dialup:p)
> 
> 
> Toby Fisher wrote
> | Hi.
> | 
> | In case Deedra hasn't picked it up yet (I know you're busy Deedra), I just 
> | wanted to say that Kirk has fixed the cut and paste bug in the 2.6 
> | kernels, so it should be safe to add Speakup to the 2.6 kernel ebuilds.
> | 
> | Cheers.
> | 
> | 
> | -- 
> | Toby Fisher	Email: toby@...
> | Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
> | ICQ: #61744808
> | 
> | --
> | gentoo-accessibility@g.o mailing list
> | 
> ---end quoted text---
Attachment:
signature.asc (This is a digitally signed message part)
Replies:
Re: 2.6 kernel and Speakup.
-- Deedra Waters
References:
2.6 kernel and Speakup.
-- Toby Fisher
Re: 2.6 kernel and Speakup.
-- Deedra Waters
Navigation:
Lists: gentoo-accessibility: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: 2.6 kernel and Speakup.
Next by thread:
Re: 2.6 kernel and Speakup.
Previous by date:
Re: 2.6 kernel and Speakup.
Next by date:
Re: 2.6 kernel and Speakup.


Updated Jun 17, 2009

Summary: Archive of the gentoo-accessibility mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.