Hi Luiz, On Mon, 2017-12-11 at 13:12 -0200, Luiz Augusto von Dentz wrote: > Hi Steve, > > On Mon, Dec 11, 2017 at 12:58 PM, <sbrown@xxxxxxxxxxxx> wrote: > > From: Steve Brown <sbrown@xxxxxxxxxxxx> > > > > Get/Set Proxy > > Get/Set Ident > > Get/Set Relay > > Set Heartbeat > > Get Publication > > Get/Set Subscription > > Ive split these into individual patches for command and then add in > the description what the expected output, etc. Btw I think it would > be > better to switch from get-set style to cmd [value], so if there is no > arguments then it just read the value, that way reduce the amount of > commands and also make the autocomplete a lot more useful since the > commands shall start with something other than set/get. > OK, I'll make the changes. This would then affect all the meshctl commands. I'll have to rearrange the parameter sequence in some of the commands so I can distinguish between a get and a set. So, where the publish commands currently are set-pub <ele-addr> <pub-addr> <app-idx> .... and get-pub <ele-addr> <model> They would become pub <ele-addr> <model> <pub-addr> .... for set and pub <ele-addr> <model> for get Do I understand this correctly? I left the subscription node and database patch separate. I'm on less solid ground here. I basically cribbed the code for bind. I added the UUID to the database as later I'd like to try to re- provision a known unprovisioned node from the database. Steve -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
