Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Stotland, Inga" <inga.stotland@intel.com>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Gix, Brian" <brian.gix@intel.com>
Subject: Re: [PATCH BlueZ] doc: Initial Bluetooth Mesh API
Date: Sat, 10 Nov 2018 20:50:20 +0100	[thread overview]
Message-ID: <20181110195020.GA27197@jhedberg-mac01.local> (raw)
In-Reply-To: <c2485caca3145e8aaaa1a8396b294b46a55b97e3.camel@intel.com>

Hi Inga,

On Thu, Nov 08, 2018, Stotland, Inga wrote:
> From D-Bus Api Design Guidelines: (
> https://dbus.freedesktop.org/doc/dbus-api-design.html#api-versioning):
> 
> "In summary, version numbers should be included in all service names,
> interface names and object paths:
> 
>     com.example.MyService1
> 
>     com.example.MyService1.InterestingInterface
> 
>     com.example.MyService1.OtherInterface
> 
>     /com/example/MyService1/Manager
> 
>     /com/example/MyService1/OtherObject
> "
> 
> I chose to do the name versioning based on the official guidelines.
> However, if we want to preserve the historical bluez approach, I don't
> mind changing it.

That's a good point you've brought up, however I think we should stick
to consistency within the project in the first place.

Johan

  reply	other threads:[~2018-11-10 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  0:49 [PATCH BlueZ] doc: Initial Bluetooth Mesh API Inga Stotland
2018-11-08 10:45 ` Johan Hedberg
2018-11-08 18:46   ` Stotland, Inga
2018-11-10 19:50     ` Johan Hedberg [this message]
2018-11-11 10:07     ` 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=20181110195020.GA27197@jhedberg-mac01.local \
    --to=johan.hedberg@gmail.com \
    --cc=brian.gix@intel.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