From: Bastien Nocera <hadess@hadess.net>
To: Pacho Ramos <pacho@gentoo.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Some patches applied on Fedora that maybe should be considered for being applied upstream
Date: Mon, 10 Feb 2014 14:40:09 +0100 [thread overview]
Message-ID: <1392039609.4417.14.camel@nuvo> (raw)
In-Reply-To: <1391935987.4666.5.camel@belkin5>
On Sun, 2014-02-09 at 09:53 +0100, Pacho Ramos wrote:
> Hello
>
> I was looking at bluez package and found some patches that maybe could
> be upstreamed. Also, I would like to know the reasons for not accepting
> them to ensure they are safe to be applied downstream by us too :)
>
> http://pkgs.fedoraproject.org/cgit/bluez.git/tree/0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch -> Does this cause any issues with systemd --user setups?
Giovanni already posted this patch earlier. There's no distribution
using systemd sessions, so this doesn't work yet.
> http://pkgs.fedoraproject.org/cgit/bluez.git/tree/0001-obex-Use-GLib-helper-function-to-manipulate-paths.patch
> http://pkgs.fedoraproject.org/cgit/bluez.git/tree/0002-autopair-Don-t-handle-the-iCade.patch
> http://pkgs.fedoraproject.org/cgit/bluez.git/tree/0004-agent-Assert-possible-infinite-loop.patch
> -> Any reason for not applying it upstream too?
I've posted those patches to the list as well.
> http://pkgs.fedoraproject.org/cgit/bluez.git/tree/0001-work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch
> -> Taking care this looks to be a really old issue, maybe using the
> workaround would be the only option for now :/
I have no hardware to test this on, I snatched it from Ubuntu's bluez 4
package.
Cheers
next prev parent reply other threads:[~2014-02-10 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 8:53 Some patches applied on Fedora that maybe should be considered for being applied upstream Pacho Ramos
2014-02-10 13:40 ` Bastien Nocera [this message]
2014-02-10 20:01 ` Pacho Ramos
2014-02-11 13:27 ` Bastien Nocera
2014-02-16 19:06 ` Pacho Ramos
2014-02-16 18:58 ` Pacho Ramos
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=1392039609.4417.14.camel@nuvo \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pacho@gentoo.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