public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Cheryl Homiak <chomiak@worldfront.com>
To: <speakup@braille.uwo.ca>
Subject: Re: two keymaps for two kernels
Date: Mon, 2 Jul 2001 17:34:01 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.30.0107021729080.7973-100000@maranatha> (raw)
In-Reply-To: <20010702154941.A395@linserver.megsinet.net>

On Mon, 2 Jul 2001, Gregory Nowak wrote:

> Hi,
>
> I think that the easiest thing to do
> would be to simply compile
> the nontalking kernel from
> a fresh source tree without speakup patched

In this case, at least in debian, that doesn't matter; we seem to be stuck
with whichever keymap was installed, be it speakup or another kernel.  I'm
sure there is a way around this, and will let somebody know if I find it
first.  I don't know what Saquib did but I did compile from a fresh kernel
tree without speaqkup compiled in.                              Cheryl



  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Saqib Shaikh
 ` Cheryl Homiak
 ` Gregory Nowak
   ` Cheryl Homiak [this message]
 Two " Cheryl Homiak
 ` Saqib Shaikh
 two " Saqib Shaikh

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.30.0107021729080.7973-100000@maranatha \
    --to=chomiak@worldfront.com \
    --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).