Re: [VOTE] Release Apache Mynewt 0.9.0-incubating-rc2

Hi, > For reference, the file that is being changed contains offsets to interrupt > vectors on ARM platforms. The new (correctly) licensed functions look > perfectly fine to me, and I think post release (and in develop) we should > replace these files. Sounds like a fine approach to me.

Re: [VOTE] Release Apache Mynewt 0.9.0-incubating-rc2

Hey Chris, On 29 May 2016, at 13:14, Christopher Collins wrote: I'm attaching git diffs between the following two revisions: a: commit when BSD license text was added (mbed repo) b: first commit to the mynewt core repo. The Mynewt files are "b" in the attached diffs. That is, "+++"

Re: [DISCUSS] A users@ mailing list for Apache Mynewt

On Sun, May 29, 2016 at 1:27 PM, David Moshal wrote: > Any reason you folks aren't using Slack, Gitter, Github or equivalent > for managing these conversation? > Mostly because we need archives of all discussions under our management. We need to keep this stuff around

Re: [VOTE] Release Apache Mynewt 0.9.0-incubating-rc2

On Sun, May 29, 2016 at 10:56:09AM -0700, Christopher Collins wrote: > The CMSIS-CORE files that Mynewt bundles fall into two categories: [...] > 2. Functional changes were made by ARM mbed before the BSD license >was added; the oldest revisions containing the BSD license text >

Re: [DISCUSS] A users@ mailing list for Apache Mynewt

Any reason you folks aren't using Slack, Gitter, Github or equivalent for managing these conversation? Dave On Sun, May 29, 2016 at 12:15 AM, Greg Stein wrote: > I don't think users@ makes sense. > > I just looked at the past 30 days, and there *might* be 10 messages. That >

Re: [VOTE] Release Apache Mynewt 0.9.0-incubating-rc2

Thanks again, Justin. My responses are inline below. I rearranged your email such that your first finding comes last, since it is the most difficult to address :). On Sun, May 29, 2016 at 11:23:25AM +1000, Justin Mclean wrote: [...] > The core release notes is out of data and talks about March

Re: [DISCUSS] A users@ mailing list for Apache Mynewt

Hi, For that purpose, the github issues feature may be used, to my mind. This feature also contributes in building a good knowledge base. I know this project isn't hosted on github and offer only a mirror there but it doesn't disallow using its features. My 2 cents, Thibaut VIARD On 29 May

Re: Correct way to add a task that only runs once

Thank you Sterling. I will take a look at the information you pointed me to. Cheers James On Sat, May 28, 2016 at 2:54 PM, Sterling Hughes wrote: > Hi James, > > Callouts are perfect for this type of function. I’d recommend > multiplexing this within the task context