Re: way too many commits

On Tue, Mar 7, 2017 at 4:25 AM, aditi hilbert <ad...@runtime.io> wrote: > > > On Mar 7, 2017, at 11:22 AM, David Brown <david.br...@linaro.org> wrote: > > > > On Tue, Mar 07, 2017 at 03:38:47AM -0600, Greg Stein wrote: > > > >> I just saw ab

way too many commits

Hey all, I just saw about two hundred commits suddenly land in the Git repository today. This seems problematic from a *community* standpoint because how could anybody else review ALL of those commits? And what if commit #10 was going in the wrong direction ... well, the following 190 went down

Re: PIC32 port

I've been doing a bunch of PIC16F688 work over the past couple years. Not sure how close that chip is to the chip/board you're working with. If you do any assembly-level work, then I'd be happy to review/support. (of course, C-level support is much more broadly available here) Lemme know, and

push more often (was: [01/50] incubator-mynewt-core git commit: ...)

commit 1 of 50 ?? This says to me: push more often. How can the mynewt community review your work, if you never push it? On Mon, Jan 23, 2017 at 9:02 PM, wrote: > Repository: incubator-mynewt-core > Updated Branches: > refs/heads/sensors_branch 6247b5afa -> 2681044e8 > >

Re: [nRF52 HAL I2C] Possible 'probe' issue?

On Tue, Dec 27, 2016 at 3:32 AM, Greg Stein <gst...@gmail.com> wrote: >... > Those addresses are *reserved* per the I2C spec. > To be explicit, I'm referring to: http://www.nxp.com/documents/user_manual/UM10204.pdf

Re: [nRF52 HAL I2C] Possible 'probe' issue?

On Mon, Dec 26, 2016 at 5:31 PM, Kevin Townsend wrote: > Hi Greg, > > Well, unexpected but the problem is indeed the faulty address > requests at the beginning and correctly setting the start > address to 0x08 causes the LSM303 to respond: > Excellent! >... > /*

Re: [nRF52 HAL I2C] Possible 'probe' issue?

Hey Kevin, all, I've done quite a bit of I2C, and Sterling pointed out this thread for me to add some thoughts. First up, the probe should start scanning at 0x08 (rather than 0x03). Per the I2C spec, Rev 6, Section 3.1.12, the first and last 8 addresses (in 7-bit addressing) are reserved. Thus

final release step (was: [RESULT][VOTE] Release Apache Mynewt ...)

On Fri, Dec 2, 2016 at 8:33 PM, Christopher Collins wrote: > Hello all, > > Voting for Apache Mynewt 1.0.0-b1-incubating-rc2 is now closed. Hi all, I was looking at prior releases, and noticed that the final step to publish the release appears to have been done wrong. No

Re: Adding C++ header guards?

Right. You don't want to apply the namespace to *other* headers, just the current file. Those other headers might be designed for inclusion by a C++ program. On Sun, Sep 11, 2016 at 2:58 PM, Peter Snyder wrote: > I think this is great too, but I don’t think it’s keeping to

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: Release dependant on LGPL

Speaking as an IPMC Member, and a Mynewt Mentor … yes, this is fine with a disclaimer in the release notes. The Incubator process is about tracking these down, and getting them fixed. Incubation releases are not expected to be *fully* conformant to all ASF policies, especially if there is a known

Re: UnPlugFest 53

Very cool! ... it's great that these events occur. I recall doing the same for WebDAV interop testing back around 1999. It sounds like mynewt's support is good, and another event or two should solidify it. Wonderful! I saw SparkFun highlighted a bunch of Bluetooth products today, too. Nice

Re: December 2015 Report

cussed and tested on > documentation site > > Date of last release: > > No release yet. > > When were the last committers or PMC members elected? > > At the start of the project (2015-10-20) > > Signed-off-by: > > [ ](mynewt) Sterling Hughes > [ ](mynewt) Jim Jagielski >

Re: Mynewt logo - request for input

"here are 4 options" ... forgot some attachments? On Tue, Nov 17, 2015 at 1:28 AM, aditi hilbert wrote: > Hi everyone, > > I’d like to get everyone's input on the Mynewt logo for the Apache > incubator website. Obviously the name is a playful play on the word > “minute” for a

Re: Minute Incubation web site

wt.incubator.apache.org/> ? Do I need to file an > infrastructure JIRA request to enable this? > > Thanks for being patient - I am still trying to figure how the pieces fit. > > thanks, > aditi > > > > On Oct 27, 2015, at 10:39 PM, Greg Stein <gst...@gmail.com>

Re: assert(), faulting traps etc

IMO, if new functions are going to be introduced, then put them into a namespace. ... "ASSERT" is who-knows-what. "MYNEWT_ASSERT" is clearly part of the mynewt OS. That said, it is ugly, so how about finding a PREFIX that can be set all our custom symbols aside, and point people into the right