From: Nico -telmich- Schottelius <nico-linux-input2008@schottelius.org>
To: linux-input@vger.kernel.org
Subject: Where to put mouse drivers?
Date: Fri, 25 Jul 2008 15:13:47 +0200 [thread overview]
Message-ID: <20080725131347.GA340@denkbrett.schottelius.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Hello dear input hackers,
on the 24th of April 2008 I wrote a message to the
gpm-mailinglist, asking where to put them. Now I am interested in
your opinion, what your idea of the mouse driver future is
a) for linux
b) for unix
c) in general
also how do you see should it work with the xorg people?
Imho one should try to minimise double fixes for mouse drivers,
but I am not sure, what your ideas are and which way you prefer
to go.
Sincerly,
Nico
PS: There is an old blog entry about it availabe here:
http://nico.schottelius.org/notizbuch-blog/archive/2008/04/24/where-to-put-mouse-drivers
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2008-07-25 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080725131347.GA340@denkbrett.schottelius.org \
--to=nico-linux-input2008@schottelius.org \
--cc=linux-input@vger.kernel.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).