multi-touch-dev team mailing list archive

[Chase Douglas <chase.douglas@xxxxxxxxxxxxx>]

On Tue, May 11, 2010 at 2:44 PM, Chase Douglas
<chase.douglas@xxxxxxxxxxxxx> wrote:
> On Mon, May 10, 2010 at 2:35 AM, Rafi Rubin <rafi@xxxxxxxxxxxxxx> wrote:
>> Anyway, if you want to adopt those patches (for the ppa, not the main kernel), I
>> don't think it will hurt, but you might need to roll them back later.
>
> I found Jiri's ntrig branch of his HID tree, so I was able to grab the
> changes directly from there. It's nice to have an extra review by
> Jiri, and he seems to be keeping up fairly well with development. The
> changes have been uploaded as version 1.3 of the multitouch package to
> ppa:chasedouglas/multitouch, and the source changes have been pushed
> to git://kernel.ubuntu.com/cndougla/multitouch.git.
>
> I'd also like to go over a few details of how we merge changes into my
> PPA, 10.04 LTS, and Maverick. For the PPA, I would be happy to throw
> in anything you want to try out. If you have patches that you are
> unsure of, and you'd like some more testing, you can send me patches
> and I'll merge them. We can elicit testing through these mailing lists
> or through ubuntu-devel depending on how much testing is warranted.
>
> For Maverick and 10.04 LTS, I would like to merge patches directly
> from at least Jiri's HID repo, with guidance from you. Feel free to
> send me an e-mail (CC'd to multitouch-devel and kernel-team) when you
> want me to grab patches, and I'll probably ping you every once in a
> while as well to ensure we keep in sync. I would also suggest running
> the daily pre-proposed kernel builds when we start merging changes
> into 10.04 LTS so you can find issues before they are even put into
> the lucid-proposed repository. Does this sound good to you?
>
> For the patches I just pulled, please let me know when you are
> comfortable proposing them for a merge into 10.04 LTS and Maverick.

I was thinking multi-touch-dev was a public mailing list. Please keep
this in mind when replying so we don't get private stuff onto
kernel-team@xxxxxxxxxxxxxxxx.

Sorry for the confusion!

-- Chase