From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Add sixaxis cable-pairing plugin
Date: Fri, 05 Jun 2009 15:48:20 +0100 [thread overview]
Message-ID: <1244213300.30768.2668.camel@cookie.hadess.net> (raw)
In-Reply-To: <1244211333.23850.46.camel@localhost.localdomain>
On Fri, 2009-06-05 at 16:15 +0200, Marcel Holtmann wrote:
>
> > You can keep personal attacks out of that. I think I've shown enough
> > patience trying to get this functionality into bluez proper.
>
> This is not personal. I am keeping a watch on the dependencies of
> BlueZ
> and I don't see any need for adding GObject to the mix for the SixAxis
> support. Feel free to convince me that GObject based gudev is really
> necessary for this. Until then I declare this bloat.
No, it's not absolutely necessary, but somebody has to reinvent the
wheel, and I'm not happy spending time doing that.
> Please remember that BlueZ will run on embedded devices with limited
> memory and space requirements. You might argue that these devices
> don't
> need SixAxis support, but I prefer to keep that option.
Yes. And if such uses exist, I'm sure they'd be happy putting some
effort into bluez and do the port from gudev to libudev themselves.
> > I won't be updating this patch, but Luiz showed interested. My patch
> > will show up in the Fedora packages shortly.
>
> That is your choice. Personally I really dislike if distros just go
> against upstream and start merging stuff, because it takes more effort
> to get it into upstream first.
All my patches are sent upstream before they go into the packages, and I
think I put quite a bit of work into this. But at the end of the day, I
only have so much time, and rewriting bits of code because the upstream
doesn't like GObject isn't what I call a good use of my time. So I'm
leaving it to somebody else to go the last mile because I can't be
bothered.
> On that point, you haven't merged the Socket fix upstream
It's not upstreamable, see the RH bugzilla. It depends on a kernel patch
that can't go upstream.
> and also the
> Wacom and UTF-8 fix could be send upstream.
They already have, and you commented on them. I still believe the UTF-8
one could be merged as-is, but I don't have a good answer for the Wacom
one, which would need more investigation.
> I know you send some version
> of these at least once or twice, but besides me also Johan could merge
> these patches.
Cheers
next prev parent reply other threads:[~2009-06-05 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 9:28 [PATCH] Add sixaxis cable-pairing plugin Bastien Nocera
2009-06-04 18:13 ` Marcel Holtmann
2009-06-05 10:42 ` Bastien Nocera
2009-06-05 13:06 ` Marcel Holtmann
2009-06-05 13:52 ` Bastien Nocera
2009-06-05 14:15 ` Marcel Holtmann
2009-06-05 14:48 ` Bastien Nocera [this message]
2009-06-05 14:56 ` Marcel Holtmann
2009-06-05 15:06 ` Bastien Nocera
2009-06-06 17:41 ` Luiz Augusto von Dentz
2009-06-06 17:51 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2009-10-09 13:19 Bastien Nocera
2009-10-11 9:40 ` Marcel Holtmann
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=1244213300.30768.2668.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.