Re: Directory re-org conversation

On Thu, Sep 15, 2016 at 03:50:25PM -0700, Sterling Hughes wrote: > Hey, > > I wanted to get this kicked off, so we can make the changes fairly > quickly after the sterly_refactor merge next week (while still giving > enough time for discussion.) [...] Sounds good to me. That would be a

Re: Directory re-org conversation

We have 2 blinky apps. We should toast the one in incubator-mynewt-core, and keep the incubator-mynewt-blinky. > On Sep 16, 2016, at 10:17 AM, Christopher Collins wrote: > > On Fri, Sep 16, 2016 at 10:04:37AM -0700, Aditi wrote: >> Would libs/bleuart is placed in

Re: Directory re-org conversation

On Fri, Sep 16, 2016 at 10:04:37AM -0700, Aditi wrote: > Would libs/bleuart is placed in net/nimble/host/profiles or > net/nimble/host/services? I am still not clear on services vs. > profiles in our directory structure. I think it should go in net/nimble/host/services. net/nimble/host/profiles

Re: Directory re-org conversation

Would libs/bleuart is placed in net/nimble/host/profiles or net/nimble/host/services? I am still not clear on services vs. profiles in our directory structure. Thanks, Aditi > On Sep 15, 2016, at 8:16 PM, will sanfilippo wrote: > > I was not referring to hw drivers in

Re: Directory re-org conversation

I was suggesting it be moved to hw/drivers/nimble. It’s similar to how other OSes do it, they tend to have the hw drivers in the drivers directory, even for the networking stack components. I don’t feel strongly about it, but thought, why shouldn’t we keep to convention. I definitely think

Directory re-org conversation

Hey, I wanted to get this kicked off, so we can make the changes fairly quickly after the sterly_refactor merge next week (while still giving enough time for discussion.) Please take this as a _rough_ first cut proposal. I want people to bikeshed this discussion, mainly because I only want