From: Johan Hedberg <johan.hedberg@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Inga Stotland <inga.stotland@intel.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/2] Directory re-org for meshctl tool
Date: Fri, 6 Jul 2018 13:41:55 +0300 [thread overview]
Message-ID: <20180706104155.GA6509@x1c.lan> (raw)
In-Reply-To: <A4890F67-3CCD-4A8A-B40F-B01F6FA240D4@holtmann.org>
Hi Marcel,
On Fri, Jul 06, 2018, Marcel Holtmann wrote:
> > This set of patches moves mechctl tool code from under bluez/mesh
> > into tools directory.
> >
> > mesh directory will be re-established with the implementation of mesh
> > daemon.
> >
> > Inga Stotland (2):
> > tools: Move meshctl tool under tools directory
> > tools: Move meshctl sources under tools/mesh directory
>
> I am missing patch 1/2 for some reason. Make sure to --cc me when
> patches might get rejected because of size by the mailing list.
I don't think it's a mailing list issue this time, since I did receive
it, and it's also visible in the archives:
https://www.spinics.net/lists/linux-bluetooth/msg76150.html
Johan
next prev parent reply other threads:[~2018-07-06 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 6:31 [PATCH BlueZ 0/2] Directory re-org for meshctl tool Inga Stotland
2018-06-22 6:31 ` [PATCH BlueZ 1/2] tools: Move meshctl tool under tools directory Inga Stotland
2018-06-22 6:32 ` [PATCH BlueZ 2/2] tools: Move meshctl sources under tools/mesh directory Inga Stotland
2018-06-28 5:50 ` [PATCH BlueZ 0/2] Directory re-org for meshctl tool Stotland, Inga
2018-07-02 16:08 ` Johan Hedberg
2018-07-06 10:30 ` Marcel Holtmann
2018-07-06 10:41 ` Johan Hedberg [this message]
2018-07-06 10:46 ` Marcel Holtmann
2018-07-06 11:05 ` 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=20180706104155.GA6509@x1c.lan \
--to=johan.hedberg@gmail.com \
--cc=inga.stotland@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox