From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [STABLE][PATCH] bluez4: add less restrictive (and hence less secure) bluetooth dbus config
Date: Sun, 12 Apr 2009 20:53:14 +0200 [thread overview]
Message-ID: <grtdaq$83m$1@ger.gmane.org> (raw)
In-Reply-To: <49E20393.6060701@xora.org.uk>
On 12-04-09 17:06, Graeme Gregory wrote:
> Khem Raj wrote:
>> Acked-by: Khem Raj<raj.khem@gmail.com>
>>
>>
>> oh the PR is jumping from 4 to 6. May be it should be 5 ?
>>
>>
> I guess stuff merged from .dev should keep compatible PR numbers.
> Otherwise it starts to get real painful to maintain.
FWIW, the next bluez patch for .stable will consist of a few combined
commits, so let's keep things in sync as much as possible.
regards,
Koen
prev parent reply other threads:[~2009-04-12 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 10:04 [STABLE][PATCH] bluez4: add less restrictive (and hence less secure) bluetooth dbus config Koen Kooi
2009-04-11 14:13 ` Koen Kooi
2009-04-12 14:40 ` Khem Raj
2009-04-12 15:06 ` Graeme Gregory
2009-04-12 18:53 ` Koen Kooi [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='grtdaq$83m$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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