From: Pacho Ramos <pacho@gentoo.org>
To: Bastien Nocera <hadess@hadess.net>
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: Sun, 16 Feb 2014 19:58:30 +0100 [thread overview]
Message-ID: <1392577110.18051.136.camel@belkin5> (raw)
In-Reply-To: <1392062509.4911.0.camel@belkin5>
El lun, 10-02-2014 a las 21:01 +0100, Pacho Ramos escribió:
> [...]
> > > 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
>
> OK, thanks :)
>
Looks to be still needed:
https://bugs.gentoo.org/show_bug.cgi?id=501120
prev parent reply other threads:[~2014-02-16 18:58 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
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 [this message]
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=1392577110.18051.136.camel@belkin5 \
--to=pacho@gentoo.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@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