public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Andi Kleen <ak@suse.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: mouse configuration in 2.6.1
Date: Wed, 21 Jan 2004 13:32:53 +0100	[thread overview]
Message-ID: <20040121123253.GA538@ucw.cz> (raw)
In-Reply-To: <20040121132337.7f8d3c79.ak@suse.de>

On Wed, Jan 21, 2004 at 01:23:37PM +0100, Andi Kleen wrote:

> (brought to you by the department of redundancy department)
> 
> The "new" and "improved" version is apparently:
> 
> psmouse_base.psmouse_proto=bare

2.6.2 will have it as:

psmouse.proto=bare

which isn't that bad.

> And 2.6.0 -> 2.6.1 silently changing to that without any documentation
> anywhere, silently breaking my mouse. And debugging it requires a lot
> of reboots because we have regressed to Windows state where every
> mouse setting change requires a reboot :-/
> 
> Sorry Rusty. You are probably the wrong target for the flame, but a
> combination of probably well intended changes including module_parm
> brought a total usability disaster here.

Keep prepared for yet another silent change (documentation _is_ getting
updated, though). And I'll don my asbestos overall ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2004-01-21 12:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040115225948.6b994a48.akpm@osdl.org.suse.lists.linux.kernel>
     [not found] ` <20040118001217.GE3125@werewolf.able.es.suse.lists.linux.kernel>
     [not found]   ` <20040117215535.0e4674b8.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]     ` <20040118081128.GA3153@werewolf.able.es.suse.lists.linux.kernel>
     [not found]       ` <20040118001708.09291455.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]         ` <20040119224219.65991501.rusty@rustcorp.com.au.suse.lists.linux.kernel>
2004-01-19 12:40           ` 2.6.1-mm4 Andi Kleen
2004-01-21  4:06             ` 2.6.1-mm4 Rusty Russell
2004-01-21  4:56               ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-21  8:40               ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:27                 ` 2.6.1-mm4 Andi Kleen
2004-01-21 12:34                   ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:46                     ` 2.6.1-mm4 Andi Kleen
2004-01-21 13:13                       ` 2.6.1-mm4 Vojtech Pavlik
2004-01-22  1:31                       ` 2.6.1-mm4 Rusty Russell
2004-01-21 12:53                     ` 2.6.1-mm4 Dmitry Torokhov
2004-01-21 12:23               ` mouse configuration in 2.6.1 Andi Kleen
2004-01-21 12:31                 ` Marcos D. Marado Torres
2004-01-21 12:42                   ` Andi Kleen
2004-01-21 12:53                     ` Marcos D. Marado Torres
2004-01-21 13:02                       ` Andi Kleen
2004-01-21 13:06                         ` Marcos D. Marado Torres
2004-01-21 13:09                     ` Dmitry Torokhov
2004-01-21 12:32                 ` Vojtech Pavlik [this message]
2004-01-22  1:14                 ` Rusty Russell

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=20040121123253.GA538@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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