Re: End-of-year Clean-up

Hi, > I don't appreciate a lot of advice and criticism from people who contribute > nothing to this process. > I would try to assume good intent from the people who responded here. You want people to contribute and grow the community, Thanks, Justin

Re: End-of-year Clean-up

Sorry, I misunderstand that you suggest this will be the new workflow. I agree that before the new process is ready, your process should continue as before since you have most experience and insight how the whole thing work together. But the committer is growing and most of us don't have that capab

Re: End-of-year Clean-up

That list just documents how I have handled the me-only workflow in the past.  It is not the workflow that is being defined by Nathan and Brennan. I don't appreciate a lot of advice and criticism from people who contribute nothing to this process.  If everyone thinks I can going continue handl

[GitHub] [incubator-nuttx-apps] masayuki2009 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file …

masayuki2009 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file … URL: https://github.com/apache/incubator-nuttx-apps/pull/2#issuecomment-570024309 > @masayuki2009 try this PR: > #3 > I can build lc823450-xgevk:ipl2 without error with this pat

Re: End-of-year Clean-up

On Wed, Jan 1, 2020 at 5:09 AM Gregory Nutt wrote: > > > > Would it make sense, then, to begin a transition period now? That is, > > start a gradual move from the current state where Greg is reviewing > > and merging all changes, toward the direction where other committers > > are reviewing/mergin

[GitHub] [incubator-nuttx-apps] xiaoxiang781216 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file …

xiaoxiang781216 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file … URL: https://github.com/apache/incubator-nuttx-apps/pull/2#issuecomment-570019713 @masayuki2009 try this PR: https://github.com/apache/incubator-nuttx-apps/pull/3 I can build

[GitHub] [incubator-nuttx-apps] xiaoxiang781216 opened a new pull request #3: Add .updated target to handle the no builtin app case correctly

xiaoxiang781216 opened a new pull request #3: Add .updated target to handle the no builtin app case correctly URL: https://github.com/apache/incubator-nuttx-apps/pull/3 Change-Id: Ia61ff63b4b1e4cb6ec52ac216626bbb76fdf3a33 Signed-off-by: Xiang Xiao --

[GitHub] [incubator-nuttx-apps] masayuki2009 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file …

masayuki2009 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file … URL: https://github.com/apache/incubator-nuttx-apps/pull/2#issuecomment-570018779 > I will take a look at this afternoon. @xiaoxiang781216 Thanks!

[GitHub] [incubator-nuttx-apps] xiaoxiang781216 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file …

xiaoxiang781216 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file … URL: https://github.com/apache/incubator-nuttx-apps/pull/2#issuecomment-570017440 I will take a look at this afternoon. ---

[GitHub] [incubator-nuttx-apps] masayuki2009 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file …

masayuki2009 commented on issue #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file … URL: https://github.com/apache/incubator-nuttx-apps/pull/2#issuecomment-570016581 Hello @xiaoxiang781216 , I noticed that this PR caused a build error for lc823450-xgevk:ipl2

Re: Podling Nuttx Report Reminder - January 2020

Hi, > It looks like the report is written. It's at: > https://cwiki.apache.org/confluence/display/NUTTX/January+2020 It up to each PPMC how they out the report together, but it needs to be submitted at: https://cwiki.apache.org/confluence/display/INCUBATOR/January2020

Re: Podling Nuttx Report Reminder - January 2020

On Tue, Dec 31, 2019 at 9:17 PM Justin Mclean wrote: > Hi, > As per instructions above you submit it here: > https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 > Thanks > Justin It looks like the report is written. It's at: https://cwiki.apache.org/confluence/display/NUTTX/Janua

Re: Podling Nuttx Report Reminder - January 2020

Hi, As per instructions above you submit it here: https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 Thanks Justin On Wed, 1 Jan 2020, 12:07 Abdelatif Guettouche, < abdelatif.guettou...@gmail.com> wrote: > Hi Justin, > > How do we submit the report? > > Thanks. > > On Sat, Dec 28,

Re: Podling Nuttx Report Reminder - January 2020

Hi Justin, How do we submit the report? Thanks. On Sat, Dec 28, 2019 at 9:03 PM Justin Mclean wrote: > > HI, > > > I'd like to contribute some edits, but I don't appear to have edit access > > to this page. > > You do now. > > Thanks, > Justin

Re: End-of-year Clean-up

On Tue, Dec 31, 2019 at 4:50 PM Gregory Nutt wrote: > Actually, I think I recommended (through implication) that we should not > use the 'dev' branch, but rather a custom, per-PR branch. A single dev > branch does not work for the reasons I mention above. The worst is that > many people are usin

Re: Have a great 2020!

Happy new year! On Wed, Jan 1, 2020, 00:28 Disruptive Solutions < disruptivesolution...@gmail.com> wrote: > Maybe not the correct place. but all the best from the Netherlands in > 2020 > > Verstuurd vanaf mijn iPhone

Have a great 2020!

Maybe not the correct place. but all the best from the Netherlands in 2020 Verstuurd vanaf mijn iPhone

[GitHub] [incubator-nuttx] masayuki2009 commented on issue #21: net: tcp: Fix compile error in tcp.h

masayuki2009 commented on issue #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21#issuecomment-570004024 > @masayuki2009 Removing support for CONFIG_NET_TCPBACKLOG altogether might be a better solution? Anyone else have an opinion to the contra

[GitHub] [incubator-nuttx] patacongo edited a comment on issue #21: net: tcp: Fix compile error in tcp.h

patacongo edited a comment on issue #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21#issuecomment-570003155 @masayuki2009 Removing support for CONFIG_NET_TCPBACKLOG altogether might be a better solution? Anyone else have an opinion to the con

[GitHub] [incubator-nuttx] patacongo commented on issue #21: net: tcp: Fix compile error in tcp.h

patacongo commented on issue #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21#issuecomment-570003155 @masayuki2009 Removing support for CONFIG_NET_TCPBACKLOG altogether might be a better solution? Anyone else have an opinion to the contrary?

[GitHub] [incubator-nuttx] masayuki2009 commented on issue #21: net: tcp: Fix compile error in tcp.h

masayuki2009 commented on issue #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21#issuecomment-570002552 > BTW: CONFIG_NET_TCPBACKLOG probably should always be enabled. Otherwise, you will miss connection requests. That configuration is a candi

[GitHub] [incubator-nuttx] patacongo commented on issue #21: net: tcp: Fix compile error in tcp.h

patacongo commented on issue #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21#issuecomment-570001685 BTW: CONFIG_NET_TCPBACKLOG probably should always be enabled. Otherwise, you will miss connection requests. That configuration is a candidat

[GitHub] [incubator-nuttx] patacongo merged pull request #21: net: tcp: Fix compile error in tcp.h

patacongo merged pull request #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [incubator-nuttx] masayuki2009 opened a new pull request #21: net: tcp: Fix compile error in tcp.h

masayuki2009 opened a new pull request #21: net: tcp: Fix compile error in tcp.h URL: https://github.com/apache/incubator-nuttx/pull/21 During build testing for spresense with the latest master, I encountered the following compile error. ``` tcp/tcp_netpoll.c: In function 'tcp_pol

Re: End-of-year Clean-up

Hi, Just a couple of comments. > * git push [--force] origin dev I’m not sure this is allowed on Apache repos, the —force that is, push is of course fine. >* Squash merge the change onto the dev branch. History can be lost this way, are you sure you want to do this? Every line of

Re: End-of-year Clean-up

On 12/31/19, Gregory Nutt wrote: > >> The workflow will be improved in the future, but any interim workflow >> will be the same flawed workflow that was used in the Bitbucket >> repositories.. with some tweaks for working together better. >> > I think that the only objective is a short term one:

Re: End-of-year Clean-up

The workflow will be improved in the future, but any interim workflow will be the same flawed workflow that was used in the Bitbucket repositories.. with some tweaks for working together better. I think that the only objective is a short term one:  To keep our heads above water until the pe

Re: End-of-year Clean-up

/* Squash merge the 'dev' branch onto master. The change on master will include both the original PR and your coding style fixes. Again, this assumes you are the only user of dev and another reason to consider using a custom temporary branch./ Thank you for sharing this step-by-step process.

Re: End-of-year Clean-up

Hi Greg and Nathan, On 12/31/19, Gregory Nutt wrote: > >> Would it make sense, then, to begin a transition period now? That is, >> start a gradual move from the current state where Greg is reviewing >> and merging all changes, toward the direction where other committers >> are reviewing/merging c

Re: End-of-year Clean-up

Would it make sense, then, to begin a transition period now? That is, start a gradual move from the current state where Greg is reviewing and merging all changes, toward the direction where other committers are reviewing/merging changes. Perhaps, for the next couple of weeks, Greg could continue

Re: nxstyle (Was Re: Working Effectively (was Point of Order))

For (1) false negatives, I just create a few simple test files and verify that nxstyle detects the error. Pretty easy. For (2) false positives, it is a little more difficult.  I use nuttx/sched to do these because it probably follows the coding standard the best.  ... There is another tes

Re: End-of-year Clean-up

On Tue, Dec 31, 2019 at 3:01 PM Gregory Nutt wrote: > > That was actually necessary. We don't want to build a huge backlog. > > I still have some fears about what is going to happen after the > holidays. My experience is that things pick up slowly after the New > Year.So we have another week

Re: nxstyle (Was Re: Working Effectively (was Point of Order))

  Perhaps a function called block_comment_width() could be called for each line.  It would return zero if the line is not the first or last line of a block comment and the position of the final '*' + 1  if is it is a block comment. The first line of a block comment starts with "/***" (pe

Re: End-of-year Clean-up

That was actually necessary. We don't want to build a huge backlog. I still have some fears about what is going to happen after the holidays.  My experience is that things pick up slowly after the New Year.    So we have another week or so until go back to their normal rates. Even then, I

Re: Future Trademark Issues

Hi, What the ALv2 license allows is different to what the ASF allows with trademarks. I suggest you read [1] and [2]. In particular, these are likely to apply here [3][4][5] Thanks, Justin 1. https://www.apache.org/foundation/marks/ 2. https://www.apache.org/foundation/marks/faq/ 3 https://ww

Re: End-of-year Clean-up

That was actually necessary. We don't want to build a huge backlog. On Tue, Dec 31, 2019 at 1:32 PM Gregory Nutt wrote: > > I propose that I merge all PRs under the "old workflow" so that we can > start the New Year with a clean slate. Let me know if anyone is opposed. > >

Re: User Email Account

I'm a relatively new NuttX user– just joined as the Apache incubator started. The amount of emails was a lot, but once I understood what's happening and why, it was relatively easy to get what I needed. I can pick out the user/help emails from the robot accounts and the Apache Incubator discussions

[GitHub] [incubator-nuttx-apps] patacongo merged pull request #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file …

patacongo merged pull request #2: fix builtin_list.c:58:10: fatal error: builtin_proto.h: No such file … URL: https://github.com/apache/incubator-nuttx-apps/pull/2 This is an automated message from the Apache Git Service. To

[GitHub] [incubator-nuttx-apps] patacongo merged pull request #1: Wapi simplify

patacongo merged pull request #1: Wapi simplify URL: https://github.com/apache/incubator-nuttx-apps/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

[GitHub] [incubator-nuttx] xiaoxiang781216 commented on issue #10: wireless: remove unnecessary flags

xiaoxiang781216 commented on issue #10: wireless: remove unnecessary flags URL: https://github.com/apache/incubator-nuttx/pull/10#issuecomment-569955525 @patacongo this PR need merge too: https://github.com/apache/incubator-nuttx-apps/pull/1 otherwise, wapi will build break. -

[GitHub] [incubator-nuttx] patacongo merged pull request #19: Unify the c++ standard library name to libxx

patacongo merged pull request #19: Unify the c++ standard library name to libxx URL: https://github.com/apache/incubator-nuttx/pull/19 This is an automated message from the Apache Git Service. To respond to the message, pleas

[GitHub] [incubator-nuttx] patacongo commented on a change in pull request #19: Unify the c++ standard library name to libxx

patacongo commented on a change in pull request #19: Unify the c++ standard library name to libxx URL: https://github.com/apache/incubator-nuttx/pull/19#discussion_r362243636 ## File path: tools/LibTargets.mk ## @@ -188,10 +188,10 @@ $(ARCH_SRC)$(DELIM)libuarch$(LIBEXT): c

[GitHub] [incubator-nuttx] xiaoxiang781216 commented on a change in pull request #19: Unify the c++ standard library name to libxx

xiaoxiang781216 commented on a change in pull request #19: Unify the c++ standard library name to libxx URL: https://github.com/apache/incubator-nuttx/pull/19#discussion_r362243316 ## File path: tools/LibTargets.mk ## @@ -188,10 +188,10 @@ $(ARCH_SRC)$(DELIM)libuarch$(LIBE

Re: Wiki has moved from NUTTXTEST to NUTTX

I agree that we should get more content in the wiki. It's locked down to prevent spam, which is the same as when Greg had it. We could change so people who have accounts can create or comment, but let's be careful. I did tweak the permissions so commiters can add people and change their permis

nxstyle (Was Re: Working Effectively (was Point of Order))

Greg, I'll finish the nxstyle & check script these days firstly and then take time to handle the two issues you mentioned if allowed. I wish I could be competent to take over full responsibility for nxstyle.c. I think it would be great if you took over primary responsibility for nxstyle.  Wi

Re: Wiki has moved from NUTTXTEST to NUTTX

I agree that we should get more content in the wiki. It's locked down to prevent spam, which is the same as when Greg had it. We could change so people who have accounts can create or comment, but let's be careful. I did tweak the permissions so commiters can add people and change their permission

[GitHub] [incubator-nuttx] patacongo merged pull request #20: psock_udp_sendto should call udp_wrbuffer_tryalloc for nonblock socket

patacongo merged pull request #20: psock_udp_sendto should call udp_wrbuffer_tryalloc for nonblock socket URL: https://github.com/apache/incubator-nuttx/pull/20 This is an automated message from the Apache Git Service. To re

[GitHub] [incubator-nuttx] patacongo commented on a change in pull request #19: Unify the c++ standard library name to libxx

patacongo commented on a change in pull request #19: Unify the c++ standard library name to libxx URL: https://github.com/apache/incubator-nuttx/pull/19#discussion_r362237598 ## File path: tools/LibTargets.mk ## @@ -188,10 +188,10 @@ $(ARCH_SRC)$(DELIM)libuarch$(LIBEXT): c

[GitHub] [incubator-nuttx] patacongo merged pull request #18: fix sim:bluetooth compiler error

patacongo merged pull request #18: fix sim:bluetooth compiler error URL: https://github.com/apache/incubator-nuttx/pull/18 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [incubator-nuttx] patacongo merged pull request #17: Net cleanup

patacongo merged pull request #17: Net cleanup URL: https://github.com/apache/incubator-nuttx/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

[GitHub] [incubator-nuttx] patacongo commented on issue #17: Net cleanup

patacongo commented on issue #17: Net cleanup URL: https://github.com/apache/incubator-nuttx/pull/17#issuecomment-569943700 To many small changes to review online. I don't see any problems with what I have looked at, but neither an I convinced that I have keen enough insight into all the

[GitHub] [incubator-nuttx] patacongo merged pull request #16: feature k210

patacongo merged pull request #16: feature k210 URL: https://github.com/apache/incubator-nuttx/pull/16 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the U

Re: Working Effectively (was Point of Order)

Greg, I'll finish the nxstyle & check script these days firstly and then take time to handle the two issues you mentioned if allowed. I wish I could be competent to take over full responsibility for nxstyle.c. Gregory Nutt 于2019年12月30日周一 下午11:31写道： > [moved from priv...@nuttx.apache.org] > > Hi

[GitHub] [incubator-nuttx] xiaoxiang781216 opened a new pull request #20: psock_udp_sendto should call udp_wrbuffer_tryalloc for nonblock socket

xiaoxiang781216 opened a new pull request #20: psock_udp_sendto should call udp_wrbuffer_tryalloc for nonblock socket URL: https://github.com/apache/incubator-nuttx/pull/20 Change-Id: I218dbbf7a588314a1034410aafad34cac802cc69 Signed-off-by: Xiang Xiao --

[GitHub] [incubator-nuttx] patacongo merged pull request #13: sama3 sam_serial.c USART selection fixes

patacongo merged pull request #13: sama3 sam_serial.c USART selection fixes URL: https://github.com/apache/incubator-nuttx/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please lo

[GitHub] [incubator-nuttx] xiaoxiang781216 opened a new pull request #19: Unify the c++ standard library name to libxx

xiaoxiang781216 opened a new pull request #19: Unify the c++ standard library name to libxx URL: https://github.com/apache/incubator-nuttx/pull/19 Change-Id: Ic5a2cd2d92759d6416f1609065f20240334e624c Signed-off-by: Xiang Xiao

[GitHub] [incubator-nuttx] patacongo merged pull request #11: Added Kconfig pin config chooser for nucleo-l432kc USARTs.

patacongo merged pull request #11: Added Kconfig pin config chooser for nucleo-l432kc USARTs. URL: https://github.com/apache/incubator-nuttx/pull/11 This is an automated message from the Apache Git Service. To respond to the

[GitHub] [incubator-nuttx] patacongo merged pull request #10: wireless: remove unnecessary flags

patacongo merged pull request #10: wireless: remove unnecessary flags URL: https://github.com/apache/incubator-nuttx/pull/10 This is an automated message from the Apache Git Service. To respond to the message, please log on t

[GitHub] [incubator-nuttx] patacongo merged pull request #9: Fixed STM32L4_NUSART for STM32L433XX.

patacongo merged pull request #9: Fixed STM32L4_NUSART for STM32L433XX. URL: https://github.com/apache/incubator-nuttx/pull/9 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [incubator-nuttx] xiaoxiang781216 opened a new pull request #18: fix sim:bluetooth compiler error

xiaoxiang781216 opened a new pull request #18: fix sim:bluetooth compiler error URL: https://github.com/apache/incubator-nuttx/pull/18 wireless/bluetooth/bt_null.c:274:10: warning: implicit declaration of function 'bt_driver_register'; did you mean 'bt_netdev_register'? [-Wimplicit-functio

End-of-year Clean-up

I propose that I merge all PRs under the "old workflow" so that we can start the New Year with a clean slate.  Let me know if anyone is opposed.

[GitHub] [incubator-nuttx] xiaoxiang781216 closed pull request #15: [DONT MERGE] Fixed NUTTX-1

xiaoxiang781216 closed pull request #15: [DONT MERGE] Fixed NUTTX-1 URL: https://github.com/apache/incubator-nuttx/pull/15 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [incubator-nuttx] xiaoxiang781216 commented on issue #15: [DONT MERGE] Fixed NUTTX-1

xiaoxiang781216 commented on issue #15: [DONT MERGE] Fixed NUTTX-1 URL: https://github.com/apache/incubator-nuttx/pull/15#issuecomment-569928557 Let's close the test pull request. This is an automated message from the Apache G

RE: Working Effectively (was Point of Order)

> If done in two separate commits, one commit to bring the file into compliance with nxstyle, followed by a second commit to make the functional change, then it will be much easier to pinpoint where exactly the bug was introduced, because bisect will find the committer that contains only the functi

Re: Wiki has moved from NUTTXTEST to NUTTX

Can we open wiki to non-committer update? This post is a good candidate: https://groups.google.com/forum/#!topic/nuttx/0TEOB6oLIJk Thanks Xiang On Sun, Dec 29, 2019 at 11:05 PM Gregory Nutt wrote: > > > > The wiki has moved from the testing space to what should be its final > > location. Everyt

[GitHub] [incubator-nuttx] xiaoxiang781216 opened a new pull request #17: Net cleanup

xiaoxiang781216 opened a new pull request #17: Net cleanup URL: https://github.com/apache/incubator-nuttx/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[DISCUSS] RE: Working Effectively (was Point of Order)

2 options are up for discussion 1.Ensure the changed/new code (per line in file) comply with the coding standard 2.Ensure the whole modified file comply with the coding standard See below for positions -Original Message- From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com] Sent: Monday, D

RE: User Email Account

Hi Justin, I would say we all understand the argument. We do not agree with how the problem is solved. Why are we making everyone drink from the fire hose? Please help make this work for everyone. Clearly, from the responses, it is not. How about we make multiple lists and arrogate them to top

FW: [PX4/Firmware] To test [PX4/NuttX] [BACKPORT] STM32F7 and STM32H7 SDMMC internal pull up usage fixed (#78) (#13787)

FYI *From:* modaltb [mailto:notificati...@github.com] *Sent:* Monday, December 30, 2019 4:13 PM *To:* PX4/Firmware *Cc:* David Sidrane; Author *Subject:* Re: [PX4/Firmware] To test [PX4/NuttX] [BACKPORT] STM32F7 and STM32H7 SDMMC internal pull up usage fixed (#78) (#13787) Tested over 300 arm

RE: Future Trademark Issues

Greg & Justin, Sorry I was running to airport and hit send too soon. >What about PX4? Doesn't PX4 carry modifications to the OS at >github.com/PX4/NuttX? Nope! - PX4 is running a snapshot of pure unadulterated upstream and between uptakes, only adds [BACKPORT] commits from contributions

Re: Apache NuttX website

Hi Greg, Brennan and all, I browsed ASF's wiki about the .asf.yaml file [1]. And I also took a look at the website [3] and its git repository [2] of another Apache Incubator project, which uses the same Jekyll template as us. It seems to me that by creating an ‘asf-site’ branch in our NuttX webs

RE: User Email Account

+1 -Original Message- From: 张铎(Duo Zhang) [mailto:palomino...@gmail.com] Sent: Monday, December 30, 2019 10:49 PM To: dev@nuttx.apache.org Subject: Re: User Email Account But I think posting so many 'hard to read' emails to the mailing list will hurt user experience and cause users to l

[GitHub] [incubator-nuttx-website] davids5 commented on issue #6: publish the website

davids5 commented on issue #6: publish the website URL: https://github.com/apache/incubator-nuttx-website/pull/6#issuecomment-569895811 @xiaoxiang781216 - not my area of expertise. This is an automated message from the Apach

[GitHub] [incubator-nuttx-website] huahang opened a new pull request #6: publish the website

huahang opened a new pull request #6: publish the website URL: https://github.com/apache/incubator-nuttx-website/pull/6 Try to publish the website according to: https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories

[GitHub] [incubator-nuttx-website] huahang opened a new pull request #5: publish the website

huahang opened a new pull request #5: publish the website URL: https://github.com/apache/incubator-nuttx-website/pull/5 Try to publish the website according to: https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories

[GitHub] [incubator-nuttx-website] huahang closed pull request #5: publish the website

huahang closed pull request #5: publish the website URL: https://github.com/apache/incubator-nuttx-website/pull/5 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [incubator-nuttx-website] xiaoxiang781216 merged pull request #4: Change wiki link from NUTTXTEST to NUTTX

xiaoxiang781216 merged pull request #4: Change wiki link from NUTTXTEST to NUTTX URL: https://github.com/apache/incubator-nuttx-website/pull/4 This is an automated message from the Apache Git Service. To respond to the messag