Re: Podling Nuttx Report Reminder - January 2020

Nice... Who is going to do this? Verstuurd vanaf mijn iPhone > Op 28 dec. 2019 om 06:11 heeft jmcl...@apache.org het volgende geschreven: > > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of

Podling Nuttx Report Reminder - January 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT. The report for your podling will

[GitHub] [incubator-nuttx] xiaoxiang781216 commented on issue #12: nxstyle improvements with No tooling

xiaoxiang781216 commented on issue #12: nxstyle improvements with No tooling URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569381487 @liuguo09 please take a look. This is an automated message from the

[GitHub] [incubator-nuttx] adamfeuer commented on issue #13: sama3 sam_serial.c USART selection fixes

adamfeuer commented on issue #13: sama3 sam_serial.c USART selection fixes URL: https://github.com/apache/incubator-nuttx/pull/13#issuecomment-569377932 @patacongo I moved the pin disambiguation to `board.h`, thanks for pointing this out. Anything else to improve or correct?

[GitHub] [incubator-nuttx] adamfeuer opened a new pull request #13: sama3 sam_serial.c USART selection fixes

adamfeuer opened a new pull request #13: sama3 sam_serial.c USART selection fixes URL: https://github.com/apache/incubator-nuttx/pull/13 ### Summary * Fixes bugs in USART console selection * Fixes a few typos in the SAMA5D27 README file ### Impact * SAMA5 USART

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

This sounds like it was... clone the repo to local. Do our thing making a feature branch.. commit to our own private repo ... Send patch (format patch) in (after nxstyle, indent, etc and README addition) and let it reviewed by sending it to central channel (was Google Group) and checkout

Re: Booting NuttX on SAMA5D27-XULT

On Fri, Dec 27, 2019 at 3:39 PM Gregory Nutt wrote: > #define PIO_UART2_RXD PIO_UART2_RXD_3 > #define PIO_UART2_TXD PIO_UART2_TXD_3 > I'll try that and revert the pinmap.h files. > Certainly you need to remove the '1' form '# undef SAMA5_HAVE_DBGU_CONSOLE > 1' in any case. > Thank for

Re: Booting NuttX on SAMA5D27-XULT

Looks like the SAMA5D2x PIO controller differs from the SAMA5D3x and D4x PIO controllers. So the PIO/ISR configuration probably needs to be updated. I'm giving this a shot, but not sure how best to tackle this. Should I look at the Linux4SAM code? Or is reading the datasheet the best way to

Re: Booting NuttX on SAMA5D27-XULT

Does NSH wait for an interrupt from the UART to read data? If so, maybe the SAMA5D27 isn't interrupting. I tried to enable PIOD interrupts, since UART2 is on PIOD, but got some compilation errors. I'll look at it more tomorrow. Yes, if you don't have RX interrupts, nothing will be read.  If

Re: Booting NuttX on SAMA5D27-XULT

I got this to appear on UART2: NuttShell (NSH) Welcome to NuttX on the SAMA5D27-XULT :) nsh> But it doesn't accept any input. Here's the changes I had to do to make it get this far: https://github.com/apache/incubator-nuttx/compare/master...adamfeuer:feature/sama5d27-xult-improvements

Re: Booting NuttX on SAMA5D27-XULT

Greg, This Microchip Atmel Github repo atmel-software-package has a bunch of example code for configuring the PIOs and interrupts for SAMA5D2 and SAMA5D3. It's seems different from the NuttX SAMA5 D2 and D3/D4 code. >From looking at this

Re: Booting NuttX on SAMA5D27-XULT

Looks like the SAMA5D2x PIO controller differs from the SAMA5D3x and D4x PIO controllers. So the PIO/ISR configuration probably needs to be updated. I'm giving this a shot, but not sure how best to tackle this. Should I look at the Linux4SAM code? Or is reading the datasheet the best way to go?

Re: Booting NuttX on SAMA5D27-XULT

I got this to appear on UART2: NuttShell (NSH) > Welcome to NuttX on the SAMA5D27-XULT :) > nsh> > But it doesn't accept any input. Here's the changes I had to do to make it get this far: https://github.com/apache/incubator-nuttx/compare/master...adamfeuer:feature/sama5d27-xult-improvements

[GitHub] [incubator-nuttx] davids5 opened a new pull request #12: nxstyle improvements with No tooling

davids5 opened a new pull request #12: nxstyle improvements with No tooling URL: https://github.com/apache/incubator-nuttx/pull/12 - Added features - outputs parse-able compiler like error format - Uses getops to parse command line. - Supports -s silence all

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

+1Singin' to choir!Sent from my Samsung Galaxy smartphone. null

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

this is a simple workflow that can fit everybody +1 On Fri, Dec 27, 2019, 22:28 Nathan Hartman wrote: > On Fri, Dec 27, 2019 at 10:45 AM Xiang Xiao > wrote: > > On Fri, Dec 27, 2019 at 10:59 PM David Sidrane > wrote: > > > Notice what happened in the repo. > > > > Yes, you manually create a

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Fri, Dec 27, 2019 at 10:45 AM Xiang Xiao wrote: > On Fri, Dec 27, 2019 at 10:59 PM David Sidrane > wrote: > > Notice what happened in the repo. > > Yes, you manually create a branch in official repo without any review process. > > > See

Re: User Email Account

sounds like a good ideea lets hope that we can still maintain the dev focus with less distraction On Fri, Dec 27, 2019, 19:43 Alan Carvalho de Assis wrote: > I think is it a good idea! It will avoid increase the volume of emails > to dev@ list. > > BR, > > Alan > > On 12/27/19, Abdelatif

Re: User Email Account

I think is it a good idea! It will avoid increase the volume of emails to dev@ list. BR, Alan On 12/27/19, Abdelatif Guettouche wrote: >> The dev list traffic may reduce after we finish the workflow discussion. >> but email from GibBox will become more and more, can we send them to >>

Re: Apache NuttX website

Sure. On Sat, Dec 28, 2019 at 1:22 AM Brennan Ashton wrote: > > That worked perfect. Xiang you should be able to assign things to me now. > > On Fri, Dec 27, 2019, 8:06 AM Abdelatif Guettouche < > abdelatif.guettou...@gmail.com> wrote: > > > Did you try this one: https://id.apache.org/ > > > >

Re: User Email Account

issues@ is a good name, let's follow the convention. On Sat, Dec 28, 2019 at 1:06 AM Abdelatif Guettouche wrote: > > > The dev list traffic may reduce after we finish the workflow discussion. > > but email from GibBox will become more and more, can we send them to > > rev...@nuttx.apache.org to

Re: Apache NuttX website

That worked perfect. Xiang you should be able to assign things to me now. On Fri, Dec 27, 2019, 8:06 AM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > Did you try this one: https://id.apache.org/ > > On Fri, Dec 27, 2019 at 4:04 PM Brennan Ashton > wrote: > > > > Unfortunately

Re: User Email Account

> The dev list traffic may reduce after we finish the workflow discussion. > but email from GibBox will become more and more, can we send them to > rev...@nuttx.apache.org to avoid the review message mess up the dev > list? While reading some projects' board reports, I came across this: > Gitbox

Re: Apache NuttX website

Did you try this one: https://id.apache.org/ On Fri, Dec 27, 2019 at 4:04 PM Brennan Ashton wrote: > > Unfortunately that website requires you to double click to edit fields > (what?) which I cannot do on mobile, so I will have to wait until Saturday > or Sunday to do that You can tag me

Re: Apache NuttX website

Unfortunately that website requires you to double click to edit fields (what?) which I cannot do on mobile, so I will have to wait until Saturday or Sunday to do that You can tag me @btashton for now. On Fri, Dec 27, 2019, 5:49 AM Xiang Xiao wrote: > Brennan, could you associate your apache

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Fri, Dec 27, 2019 at 10:59 PM David Sidrane wrote: > > Hi Greg, > > I have used Bit bucket and Github and others SCM. I have had more positive > Github experiences > > For me Github has always been a better tool except for the killer feature on > BB of meld like diff. > > I am not working

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

I use GH on all projects that accept it and it is a breeze to work with PR. I clone the project add my commit and make a PR that can be reviewed and amended depending on the case. BB was harder to use and I felt that the edit and review in place were some of the drawbacks. I agree that with

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Again, think of you are a contributor, not a commiter. Not all contributors are committers, you should not use a different (official) workflow comparing to them. That's my point. Everything falls into place neatly when you consider the workflow from the point of view of the NuttX end-user /

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Again, think of you are a contributor, not a commiter. Not all contributors are committers, you should not use a different (official) workflow comparing to them. That's my point. David Sidrane 于2019年12月27日周五 下午10:59写道： > Hi Greg, > > I have used Bit bucket and Github and others SCM. I have had

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi Greg, I have used Bit bucket and Github and others SCM. I have had more positive Github experiences For me Github has always been a better tool except for the killer feature on BB of meld like diff. I am not working against anyone. I am trying to share what I know about GH, the mistakes I

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Fri, Dec 27, 2019 at 9:26 AM Gregory Nutt wrote: > Hi, Nathan, > > I remember promising to help you with the workflow document a few days > ago. I am having a little trouble following your outline. Fleshing it > out a little more would probably be helpful to keep us on track. > > Anyway...

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

>I do not know what is the problem for receiving patch from email. Obviously most people will just use git and GitHub but providing another way is also fine? It is not have a problem with the project taking patches. It is just not the ONLY option. > I do not fully get what is the point of your

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Hi, Nathan, I remember promising to help you with the workflow document a few days ago.  I am having a little trouble following your outline.  Fleshing it out a little more would probably be helpful to keep us on track. Anyway... I did make some first small changes today and I am addressing

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

+1 I agree with all that you have said. I would just add the WHY. Let's not teach bad habits (HAM Story) Yes document them all and describe why fall a back may be needed. We might even want to rate them as preferred and acceptable (Just like the NuttX Coding Standard document does) David

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

I do not know what is the problem for receiving patch from email. Obviously most people will just use git and GitHub but providing another way is also fine? I do not fully get what is the point of your story as I'm not good at reading English stories but if you mean that people should move on to

[GitHub] [incubator-nuttx-website] davids5 merged pull request #3: Still Wrong

davids5 merged pull request #3: Still Wrong URL: https://github.com/apache/incubator-nuttx-website/pull/3 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

On Fri, Dec 27, 2019 at 8:26 AM David Sidrane wrote: > Nathan, > > I am not sure if this is a terminology issue or just being new to github. > (I > feel you. We have all been there!) > > Where do they submit the PR from? > > >

[GitHub] [incubator-nuttx-website] davids5 opened a new pull request #3: Still Wrong

davids5 opened a new pull request #3: Still Wrong URL: https://github.com/apache/incubator-nuttx-website/pull/3 Same issue leading [ This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [incubator-nuttx-website] xiaoxiang781216 merged pull request #1: Fixed errant ']' README.MD

xiaoxiang781216 merged pull request #1: Fixed errant ']' README.MD URL: https://github.com/apache/incubator-nuttx-website/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log

Re: Apache NuttX website

Brennan, could you associate your apache and github account here? https://whimsy.apache.org/roster/committer/btashton And enable 2FA here: https://gitbox.apache.org/setup/ So you can review the future website related patch. The web technology is far beyond my knowledge, I can't do the depth review

[GitHub] [incubator-nuttx-website] xiaoxiang781216 merged pull request #2: fix apache git repo links

xiaoxiang781216 merged pull request #2: fix apache git repo links URL: https://github.com/apache/incubator-nuttx-website/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log

Re: 404 on site (Project status Nuttx)

On Fri, Dec 27, 2019 at 9:27 PM Gregory Nutt wrote: > > > You.can try the generated pages here: > > https://apache-nuttx-website.github.io/ > > > How would you navigate to the Confluence Wiki from these pages? Or am I > just confused? > > At the middle of https://apache-nuttx-website.github.io:

RE: 404 on site (Project status Nuttx)

-Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Friday, December 27, 2019 5:27 AM To: dev@nuttx.apache.org Subject: Re: 404 on site (Project status Nuttx) > You.can try the generated pages here: > https://apache-nuttx-website.github.io/ > How would you

RE: 404 on site (Project status Nuttx)

> Confused Yes - I was too - this is the website not wiki. Look here https://whimsy.apache.org/roster/ppmc/nuttx under Naming that is the 404 This is the link that works https://apache-nuttx-website.github.io/ > The Confluence database is separate, correct? If we were to make Yes. >

Re: 404 on site (Project status Nuttx)

You.can try the generated pages here: https://apache-nuttx-website.github.io/ How would you navigate to the Confluence Wiki from these pages? Or am I just confused? The Confluence database is separate, correct?  If we were to make Confluence changes under this temporary URL, would they be

RE: Software release life cycle choices could have implications on workflow (was RE: Single Committer)

Nathan, I am not sure if this is a terminology issue or just being new to github. (I feel you. We have all been there!) Where do they submit the PR from? https://stackoverflow.com/questions/14906187/how-to-submit-a-pull-request-from-a-cloned-repo The only other option is to email patches. I

Are you familiar with the HAM story? (Was Are you failure with the HAM Story?)

If I could only spell and see my errors. dyslexics untie[1] 1 http://www.specialcompass.ca/shakiras-blog/2017/10/23/dyslexic-untie On 2019/12/20 21:09:17, David Sidrane wrote: > All, > > This is one of my favorite Lessons that I learned... reposted from Private > > Are you failure with the

Re: How to change git description?

On Fri, Dec 27, 2019 at 5:49 PM 张铎(Duo Zhang) wrote: > > File an infra issue? > > And git-wip-us has been deprecated, now we use gitbox. > > https://gitbox.apache.org/repos/asf/incubator-nuttx > > https://gitbox.apache.org/repos/asf/incubator-nuttx-apps > Hans send a patch fix it, please take a

[GitHub] [incubator-nuttx-website] huahang commented on issue #1: Fixed errant ']' README.MD

huahang commented on issue #1: Fixed errant ']' README.MD URL: https://github.com/apache/incubator-nuttx-website/pull/1#issuecomment-569262429 LGTM This is an automated message from the Apache Git Service. To respond to the

[GitHub] [incubator-nuttx-website] huahang opened a new pull request #2: fix apache git repo links

huahang opened a new pull request #2: fix apache git repo links URL: https://github.com/apache/incubator-nuttx-website/pull/2 Signed-off-by: hans This is an automated message from the Apache Git Service. To respond to the

RE: 404 on site (Project status Nuttx)

Did you see the PR for the README.md There was a typo in the MD. But the Link looks wrong to me and I would not know where to point it at this point. -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Friday, December 27, 2019 4:10 AM To: dev@nuttx.apache.org

Re: 404 on site (Project status Nuttx)

I open a JIRA to get INFRA help: https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-19634 On Friday, December 27, 2019, David Sidrane wrote: > What is in the way of fixing the 404? > > > > -Original Message- > From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] > Sent:

RE: 404 on site (Project status Nuttx)

The [GitHub] tab lands on one repo. Do you need a landing page or repo? That lists all the other repos? -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Friday, December 27, 2019 4:03 AM To: dev@nuttx.apache.org Subject: Re: 404 on site (Project status Nuttx)

RE: 404 on site (Project status Nuttx)

What is in the way of fixing the 404? -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Friday, December 27, 2019 3:59 AM To: dev@nuttx.apache.org Subject: Re: 404 on site (Project status Nuttx) No, this git just has the website content. The git contain both

Re: 404 on site (Project status Nuttx)

You.can try the generated pages here: https://apache-nuttx-website.github.io/ On Friday, December 27, 2019, Xiang Xiao wrote: > No, this git just has the website content. > The git contain both Brennan and Hans change even Justin, you can see > the full commit here: >

Re: 404 on site (Project status Nuttx)

No, this git just has the website content. The git contain both Brennan and Hans change even Justin, you can see the full commit here: https://github.com/apache/incubator-nuttx-website/commits/master https://nuttx.apache.org should host the content generated from this git which has a link to wiki

Re: 404 on site (Project status Nuttx)

How does this effect ongoing Confuence development on Brennan's old site?  This needs to move to a new URL. What is the URL? Will additional changes to Brennan's site be lost?Thanks,GregSent from Samsung tablet. Original message From: Hans Date: 12/27/19 4:16 AM (GMT-06:00)

Re: How to change git description?

Here is JIRA: https://issues.apache.org/jira/browse/INFRA-19633 On Fri, Dec 27, 2019 at 5:49 PM 张铎(Duo Zhang) wrote: > > File an infra issue? > > And git-wip-us has been deprecated, now we use gitbox. > > https://gitbox.apache.org/repos/asf/incubator-nuttx > >

Re: Workflow Development

On Fri, Dec 27, 2019 at 12:24 AM Justin Mclean wrote: > > > A chicken and egg problem: he want to do the contribution become the > > committer, but the contribution need be done with committer' rights. > > No it is not, people can contribute without having a commit bit. Like I said before,

Re: 404 on site (Project status Nuttx)

Hi mentors, Xiang has already imported the project website Brennan created into the official Apache NuttX Website repository. https://github.com/apache/incubator-nuttx-website How can it be published to https://nuttx.apache.org/? Thanks, Huahang On Fri, Dec 27, 2019 at 5:24 PM wrote: > >

Re: How to change git description?

File an infra issue? And git-wip-us has been deprecated, now we use gitbox. https://gitbox.apache.org/repos/asf/incubator-nuttx https://gitbox.apache.org/repos/asf/incubator-nuttx-apps Xiang Xiao 于2019年12月27日周五 下午4:59写道： > https://git-wip-us.apache.org/repos/asf?p=incubator-nuttx.git >

404 on site (Project status Nuttx)

http://incubator.apache.org/projects/nuttx.html Gives back 404's when clicking on links like Board Reports and Website. And Wiki is nog active yet? No dates are filled here? Is this not the right project overview site? Roadmap/status? Ben

How to change git description?

https://git-wip-us.apache.org/repos/asf?p=incubator-nuttx.git It's better to change the description from "Apache nuttx" to "Apache NuttX" https://git-wip-us.apache.org/repos/asf?p=incubator-nuttx-apps.git It's better to change the description from "Apache nuttx" to "Apache NuttX Apps"? The github