From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] bluetooth: update rootfile
Date: Fri, 03 Jun 2016 16:43:51 +0100 [thread overview]
Message-ID: <1464968631.24121.55.camel@ipfire.org> (raw)
In-Reply-To: <c02935f87325f5a5196b14f80a0bc2f6@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
There was none after the last nightly build:
http://nightly.ipfire.org/next/2016-06-02T15%3A34%3A11%2B01%3A00-c935a269/
Is this possibly dependent on the dbus patch?
-Michael
On Fri, 2016-06-03 at 17:42 +0200, Marcel Lorenz wrote:
> Hi,
>
> removes only "changes in roorfile" message after build.
>
> Marcel
>
> Am 2016-06-03 17:14, schrieb Michael Tremer:
> >
> > Hi,
> >
> > context?
> >
> > -Michael
> >
> > On Fri, 2016-06-03 at 07:37 +0200, Marcel Lorenz wrote:
> > >
> > > Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
> > > ---
> > > config/rootfiles/packages/bluetooth | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/config/rootfiles/packages/bluetooth
> > > b/config/rootfiles/packages/bluetooth
> > > index 267e40e..346441b 100644
> > > --- a/config/rootfiles/packages/bluetooth
> > > +++ b/config/rootfiles/packages/bluetooth
> > > @@ -5,6 +5,7 @@ etc/bluetooth/input.conf
> > > etc/bluetooth/main.conf
> > > etc/bluetooth/network.conf
> > > etc/bluetooth/rfcomm.conf
> > > +#etc/dbus-1/system.d
> > > etc/dbus-1/system.d/bluetooth.conf
> > > #lib/udev/rules.d/24-bluetooth.rules
> > > lib/firmware/BCM-LEGAL.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-03 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 5:37 Marcel Lorenz
2016-06-03 15:14 ` Michael Tremer
2016-06-03 15:42 ` Marcel Lorenz
2016-06-03 15:43 ` Michael Tremer [this message]
2016-06-03 17:01 ` Marcel Lorenz
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=1464968631.24121.55.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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