From: Henrik Rydberg <rydberg@bitmath.org>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Chris Bagwell <chris@cnpbagwell.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Alternative approach to MT_TOOL_ENVELOPE
Date: Thu, 16 Dec 2010 15:35:50 +0100 [thread overview]
Message-ID: <4D0A23C6.7000308@bitmath.org> (raw)
In-Reply-To: <4D092E34.8060002@canonical.com>
>
> I do think that MT is complex enough that related documentation should
> be in multi-touch-protocol.txt, though. Anywhere I discussed MT in
> evdev-codes.txt I referred the reader to the other file. Henrik, does
> that sound good to you?
Yep, thanks.
>> I think it will be invaluable to document this stuff for driver
>> writers and apps but I'm not sure yet what level needs to be enforced.
>
> That's the biggest issue I see right now. Do we want black and white
> specificity? For example, using terms like "must" and "may not" etc. Or
> do we want the document to merely hold best practices while not
> proscribing exact details? I think even with exact details we can loosen
> them if needed, but that has its own can of worms.
It will most likely need to be judged on a case-by-case basis.
Thanks,
Henrik
next prev parent reply other threads:[~2010-12-16 14:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 10:26 [PATCH 0/4] Alternative approach to MT_TOOL_ENVELOPE Henrik Rydberg
2010-12-15 17:40 ` Chase Douglas
2010-12-15 19:36 ` Henrik Rydberg
2010-12-15 21:13 ` Chase Douglas
2010-12-16 14:41 ` Henrik Rydberg
2010-12-15 20:41 ` Chris Bagwell
2010-12-15 21:08 ` Chase Douglas
2010-12-16 14:35 ` Henrik Rydberg [this message]
2010-12-16 0:19 ` Peter Hutterer
-- strict thread matches above, loose matches on Subject: below --
2010-12-14 21:21 Chase Douglas
2010-12-14 21:38 ` Chase Douglas
2010-12-14 22:12 ` Dmitry Torokhov
2010-12-15 0:21 ` Chase Douglas
2010-12-15 1:37 ` Henrik Rydberg
2010-12-15 7:25 ` Dmitry Torokhov
2010-12-15 17:31 ` Chase Douglas
2010-12-15 20:25 ` Chris Bagwell
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=4D0A23C6.7000308@bitmath.org \
--to=rydberg@bitmath.org \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
/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).