From: BenH <bh40@calva.net>
To: Tom Rini <trini@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org, hughc@babcockbrown.com
Subject: Re: USB Mouse Changed in 2.2.14
Date: Thu, 13 Jan 2000 11:25:35 +0100 [thread overview]
Message-ID: <20000113112535.015369@192.168.1.10> (raw)
In-Reply-To: <Pine.LNX.4.10.10001121541450.18221-100000@opus.bloom.county>
On Wed, Jan 12, 2000, Tom Rini <trini@kernel.crashing.org> wrote:
>Yes, yes it has. And since Paul didn't sync up to something current
>enough ( :(((( ) 2.2.14 and 2.4.0 are looking lilke they'll have different
>userland configs still.
Paul just included the hack to put back the mouse at device 10 32. rsync
again, it should work.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-13 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-13 1:10 USB Mouse Changed in 2.2.14 Hugh Caley
2000-01-12 22:42 ` Tom Rini
2000-01-13 10:25 ` BenH [this message]
2000-01-13 17:16 ` hughc
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=20000113112535.015369@192.168.1.10 \
--to=bh40@calva.net \
--cc=hughc@babcockbrown.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).