Many feature is added, here has the detailed information:
https://github.com/ARMmbed/littlefs/releases
Should we use dev mail list for patch until the github workflow is ready?
Thanks
Xiang
Yes, the code still commit to bithucket, I mean the code review:).
On Wed, Dec 11, 2019 at 5:25 PM 张铎(Duo Zhang) wrote:
>
> We could still use bitbucket I think.
>
> Xiang Xiao 于2019年12月11日周三 下午2:09写道：
>
> > Many feature is added, here has the detailed information:
&
I think we can keep apps and nuttx as two separate gits, mynewt even has dozen:
https://gitbox.apache.org/repos/asf?s=mynewt
It's enough to just change tag to branch for incoperating the potential bugfix.
Thanks
Xiang
On Fri, Dec 13, 2019 at 9:53 PM Gregory Nutt wrote:
>
> Another thing to
another patch fix warning: 'g_nullstring' defined but not used.
Thanks
Xiang
It seems that I can't attach the file to dev@nuttx.apache.org:(.
My attachment in previous email also lose:
https://lists.apache.org/thread.html/9bc6f92e39b9d2f401e1554c0e3270d574067ff608d13df1c1c1b11e%40
Justin, can we send the attachment to dev@nuttx.apache.org?
On Wed, Dec 18, 2019 at 12:17
The new wiki look great, thanks your hard work, Brennan!
-Original Message-
From: David Sidrane
Sent: 2019年12月17日 17:53
To: dev@nuttx.apache.org
Subject: RE: [nuttx] Wiki Backup
Looking good! Thank you Brennan!
-Original Message-
From: Brennan Ashton
But I think that someone from committer need convert patch to the
github pull request, and then pass all automatic check before
submitting the change.
To ensure the commit quality, nobody can bypass the workflow we will setup.
On Mon, Dec 16, 2019 at 9:48 AM Gregory Nutt wrote:
>
> Just a guess,
Yes, GitHub has the standard workflow, we just need insert our special
requirement(style, build and test) into it:
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/github-flow
Here is one example mynewt:
https://github.com/apache/mynewt-core/pull/2126
Thanks
Xiang
On
In the transition phase, only you(Greg) can merge PR or create branch,
other PPMC member shouldn't touch the official repo.
So I think there isn't difference between bitbucket and apache? we
just change the repo location, no more change until the new workflow
setup.
On Sat, Dec 21, 2019 at 9:15
But to avoid we lose the confidence and contribution in the transition
phase, it's better that Greg has the special right to be the only
person who review and commit the code until the community agree and
setup the new workflow.
I suppose that the special period should be short and around several
Hi all,
I would suggest that we still follow the original process before the
new workflow is ready which mean that:
1.We post the patch to dev@nuttx.apache.org or
2.Send the pull request to https://github.com/apache/incubator-nuttx
3.Only Greg can commit the patch to apache/github repo
I am seeing
This is David's suggested workflow, but it still in the discussing or
voting process?
Before we get the approvement from community, we can't apply this
process now because its' unfailr to other upcomming potential
suggestion.
So my suggestion is still to keep the old process: Greg review and
Should we enable the attachment before the new workflow settle? so the
traditional workflow can transfer from google group to here
immediately.
Thanks
Xiang
On Wed, Dec 18, 2019 at 5:55 AM Justin Mclean wrote:
>
> Hi,
>
> Other project use in no particular order:
> - GitHub issues
> - JIRA
> -
I think we can learn the good practice from PX4, but shouldn't take
all without any justification.
PX4 has the mature workflow, maybe we can extract the core OS part as
our base to boost the initial setup.
The important thing now is to define the high level workflow and vote
in the community.
Then
On Wed, Dec 25, 2019 at 9:55 PM David Sidrane wrote:
>
> Hi Xiang,
>
> On 2019/12/25 05:36:14, Xiang Xiao wrote:
> > Yes, I agree that we shouldn't make the workflow too hard to scare
> > people for contribution.
> > NuttX isn't a new project, it's open source for m
On Wed, Dec 25, 2019 at 2:30 PM 张铎(Duo Zhang) wrote:
>
> Xiang Xiao 于2019年12月25日周三 下午1:36写道：
>
> > Yes, I agree that we shouldn't make the workflow too hard to scare
> > people for contribution.
> > NuttX isn't a new project, it's open source for more than ten years
&g
box.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
> > It's better to change the description from "Apache nuttx" to "Apache 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
Mon, Feb 10, 2020 at 10:44 PM Adam Feuer wrote:
>
> > Xiang,
> >
> > Thank you! It's late here in Seattle WA USA; I'll try it tomorrow!
> >
> > cheers
> > adam
> >
> > On Mon, Feb 10, 2020 at 10:40 PM Xiang Xiao
> > wrote:
> >
&g
On Tue, Feb 11, 2020 at 11:48 PM Peter Van Der Perk
wrote:
>
> >I believe that both sides would be the same. Both would use BSD sockets,
> >SocketCAN would be added to the network stacks, and the CAN drivers would be
> >a network drivers.
> >
> >Your picture shows the existing implementation
Adam, please follow this instruction if you want to connect the real
network instead loopback:
https://github.com/apache/incubator-nuttx/pull/249/commits/1b489449f790c2b4618df9133114bb05f0132e87
The setup is very simple, you don't need config any IP address manually.
Thanks
Xiang
On Tue, Feb 11,
> nsh> ifconfig
> > lo Link encap:Local Loopback at UP
> > inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0
>
>
>
>
> Do you have a defconfig that I can run that will bring up NSH? Or any
> defconfig that will show the network is working?
>
> chee
?
>
> cheers
> adam
>
> On Mon, Feb 10, 2020 at 8:50 PM Xiang Xiao
> wrote:
>
> > Do you enable CONFIG_SIM_NET_BRIDGE?
> > To get the basic network, the below options are required:
> > CONFIG_NET=y
> >
> > CONFIG_NETINIT_DHCPC=y
&
ethernet interface isn't getting a MAC address... it's all 0's. Your
> virtual ethernet has one. So something is wrong with the netinit for my
> interface.
>
> cheers
> adam
>
> On Mon, Feb 10, 2020 at 10:03 PM Xiang Xiao
> wrote:
>
> > It's my full config, but to a
On Tue, Feb 25, 2020 at 11:59 PM Gregory Nutt wrote:
>
> Hi,
> >>
> >>> i meant that, if userspace wants to read some kernel memory, it can pass
> >>> the kernel pointer to eg. write system call as the buffer argument,
> >>> and then read the contents of the file.
> >> I guess I still don't
On Wed, Feb 26, 2020 at 12:34 AM Gregory Nutt wrote:
>
> On 2/25/2020 10:26 AM, Xiang Xiao wrote:
> > On Tue, Feb 25, 2020 at 11:59 PM Gregory Nutt wrote:
> >> Hi,
> >>>>> i meant that, if userspace wants to read some kernel memory, it can pass
> >>
For kernel build, all symbols need be resolved:
1.We need add libapps.a into LDLIBS to resolve nsh_*, which remove
accidentally in commit 4ee39e208048f075860
2.LDLIBS should contain libproxy.a to resolve sched_*, and libc.a for
fprintf, but these library should in LDLIBS automatically.
Thanks
On Wed, Feb 26, 2020 at 12:57 PM Takashi Yamamoto
wrote:
>
> hi,
>
> On Wed, Feb 26, 2020 at 1:36 PM Xiang Xiao wrote:
> >
> > For kernel build, all symbols need be resolved:
> > 1.We need add libapps.a into LDLIBS to resolve nsh_*, which remove
> > accide
The email send from Apache Jenkins Server ,
it seems that we can receive it now:
https://lists.apache.org/thread.html/r304bcb41f842b402d5ab95eb29f59283b2d3e2ad5a728da07d382ae8%40
Thanks
Xiang
On Sat, Feb 29, 2020 at 6:25 AM Justin Mclean wrote:
>
> Hi,
>
> > But the dev maillist hasn't got the
Since the build system has many issue with parallel build, Haitao and
I try to fix these issues in the recent weeks, but still has several
random failure hard to fix. Yes, it seem that it's better to send the
nightly build result to dev list so other people can help to fix the
issue. We will
+1
Except someone take the commitment to make Windows native stable and
functional as other host in the 1st Apache release.
Thanks
Xiang
On Tue, Jan 21, 2020 at 2:16 PM Phani Kumar wrote:
>
> -1
>
> We should keep windows support. It would help NuttX in long run.
>
> With best regards,
> Phani.
ike to follow and avoid they make the same mistake in the new PR.
>
>
> On Thu, Mar 5, 2020 at 11:05 AM Xiang Xiao wrote:
> >
> > On Thu, Mar 5, 2020 at 5:10 PM Abdelatif Guettouche
> > wrote:
> > >
> > > Hi,
> > >
> > > We do n
On Thu, Mar 5, 2020 at 5:10 PM Abdelatif Guettouche
wrote:
>
> Hi,
>
> We do not squash commits unless they are related (Which should have been
> done by the OP in the firsr place).
But even the patch related each other, it's better to keep the
individual small patch instead merging into one big
As I remember correctly, Brennan want to take the release manager role
to finish the first release.
On Thu, Feb 27, 2020 at 9:24 AM Nathan Hartman wrote:
>
> On Wed, Feb 26, 2020 at 8:05 PM Justin Mclean
> wrote:
> > Where is the project at in moving forward to make it’s next release?
>
> I
Now the nightly build include all most boards under arm, mips, risc-v,
sim and x86, there is still some improvement need from community:
1.Some boards under arm, risc-v and sim still can't pass the build,
you can see the full list here(start with -):
to that related
people provide the support.
On Thu, Feb 27, 2020 at 9:23 PM David Sidrane wrote:
>
> I am unclear about the build status and what has been added and if all the
> configs are in the test list. As I read the email from Xiang Xiao - all the
> builds do not build yet
On Thu, Mar 5, 2020 at 10:22 PM Gregory Nutt wrote:
>
> The decision to squash or not will be left to the best judgement of the
> committer.
Yes, committer could give the suggestion, or even decline the PR, but
it isn't good practice to directly do squash without any discussion.
Even worse,
stom board with stm32f405, using latest original
> nuttx and apps.
>
> I had tried to increase twice CONFIG_EXAMPLES_USRSOCKTEST_STACKSIZE, it
> didn't help, assertion in the same place.
>
> сб, 22 февр. 2020 г. в 18:11, Xiang Xiao :
>
>> The semaphore assertion look l
David, patch is here:
https://github.com/apache/incubator-nuttx-apps/pull/95
Thanks
Xiang
On Tue, Feb 25, 2020 at 8:26 PM David Sidrane wrote:
>
> Hi Takashi,
>
> Thanks for looking at this.
>
> Yes. Linux
>
> To test it should I revert the revert and then apply the commit or is there
> a PR I
On Tue, Feb 25, 2020 at 10:08 PM Gregory Nutt wrote:
>
>
> > i meant that, if userspace wants to read some kernel memory, it can pass
> > the kernel pointer to eg. write system call as the buffer argument,
> > and then read the contents of the file.
> I guess I still don't understand. Access is
I will merge it.
On Tue, Feb 4, 2020 at 12:50 PM Haitao Liu wrote:
>
> Hi, Greg,
> Thanks to Miguel's careful review, could you please help to finish the PR
> merge?
> Then I and Miguel can continue the development with more PRs and refinement.
>
> Gregory Nutt 于2020年1月31日周五 下午11:30写道：
>
> >
>
Yang,
Could you share more background information? we are very interesting
the possibility to call Linux side API.
For upstream, if each patch is small and independent, you can send PR
directly to:
https://github.com/apache/incubator-nuttx
Or Greg could create a branch so you can do the work on
Greg,
I saw several patch for z80, does the problem get fixed or we need take a look?
Thanks
Xiang
On Fri, Feb 21, 2020 at 4:25 AM Gregory Nutt wrote:
>
> Here is a little more detail about the error:
> >
> > Here are the problems that I see now:
> >
> > 1. The eZ80 COMPILE target
I amn't familiar with CAN, but is it possible to implement a general
CAN MAC driver on top of CAN CHAR driver like this?
+---+
| NuttX Network driver |
| ++ ++ |
| |Syscall glue| |BSD Socket | |
| || |glue| |
|
Could you register a confluence account? so you can modify the page directly.
On Fri, Feb 21, 2020 at 10:51 PM Florian Wehmeyer wrote:
>
>
> Hi all,
>
> just tested the
>
> "Updating a Release System with ELF Programs – No Symbol Tables"
>
>
On Sat, Feb 22, 2020 at 12:58 AM Nathan Hartman
wrote:
>
> On Fri, Feb 21, 2020 at 11:21 AM David Sidrane
> wrote:
>
> > This is what I did:
> >
> > For apps and nuttx git fetch nuttx
> > For apps and nuttx git checkout master
> > For apps and nuttx git reset -hard nuttx/master
> >
> > make
The attachment may be filtered by apache server, please submit a PR to:
https://github.com/apache/incubator-nuttx/pulls
Or change the patch suffix and resend again.
Thanks
Xiang
On Sat, Feb 22, 2020 at 5:33 AM GOERLITZ Otmar
wrote:
>
> Dear Madams and Sirs,
>
>
>
> the file
Oleg, try this PR:
https://github.com/apache/incubator-nuttx/pull/354
with Masayuki and my patch, all test in usrsocktest should pass now.
Actually, all fail is very minor:
1.Set the different errno
2.Foget to check NULL pointer
3.Don't zero the sockaddr padding bytes
,usrsock work well very even
or update the PR to trigger the precheck again.
> And add the [![Build Status] to the README.md
>
>
>
>
>
>
>
>
>
> -Original Message-
> From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com]
> Sent: Friday, February 21, 2020 9:55 PM
> To: dev@nuttx.apache.org
>
t;
> сб, 22 февр. 2020 г. в 13:38, Xiang Xiao :
>
> > Oleg, try this PR:
> > https://github.com/apache/incubator-nuttx/pull/354
> > with Masayuki and my patch, all test in usrsocktest should pass now.
> > Actually, all fail is very minor:
> > 1.Set the different
cheers
> adam
>
> On Thu, Feb 13, 2020 at 4:49 AM Xiang Xiao
> wrote:
>
> > On Thu, Feb 13, 2020 at 10:33 AM Adam Feuer wrote:
> > >
> > > Thanks to Xiang and Greg, I got Internet networking running in the
> > > simulator.
> >
Here is a demo fix for one of IOB deadlock recently :
commit 2d0baa779d997f39b8121f5965f8125184e80d71
Author: chao.an
Date: Thu Jan 16 14:20:09 2020 -0300
net/udp: break the network lock to avoid deadlock
Author: chao.an
net/udp: break the network lock to avoid deadlock
Ubuntu 18.04 run on VirtualBox with NAT. For me, I just spend the time
with the hardware my project will use or the simulator.
On Mon, Feb 10, 2020 at 11:53 PM Takashi Yamamoto
wrote:
>
> which host os are you using?
>
> On Tue, Feb 11, 2020 at 12:46 AM Xiang Xiao wrote:
> &
How about we host the active project porting on github.com/nuttx? so
the community could share the work.
On Mon, Feb 10, 2020 at 11:11 PM Gregory Nutt wrote:
>
>
> > I wanted to use mqtt on nuttx.
> > I found a nuttx port of paho.mqtt.embedded-c in spresense sdk. [1]
> > I modified it for my
Alin,
do you upstream your work? I can't find here:
https://github.com/micropython/micropython/tree/master/ports
There even has a zephyr porting.
It's greet if you can upstream nuttx porting to the mainline.
On Tue, Feb 11, 2020 at 12:04 AM Alin Jerpelea wrote:
>
> Hi
>
> as a best practice
Yes, we also hit the similar issue in the WiFi testing and the fix is
ready, I will send the patch today.
Thanks
Xiang
On Sat, Jan 11, 2020 at 12:59 AM Gregory Nutt wrote:
>
> Issue received on Google group. Any insightes? Xaio Xiang? There have
> been a lot of networking changes recently.
>
On Sat, Jan 11, 2020 at 12:42 PM Adam Feuer wrote:
>
> After debugging, it seems like the TCP connection is not being closed
> correctly, and the client receive times out.
>
> Could this be the TCP close problem that has been reported? When was it
> introduced? I'd like to go back to a previous
On Sun, Jan 12, 2020 at 2:20 AM Gregory Nutt wrote:
>
>
> > I fixed this section of code because it had ETIMEOUT instead of
> > ETIMEDOUT and so caused a compilation failure.
> >
> > Looking more carefully, net_timedwait() will return -ETIMEDOUT on the
> > timeout. So shouldn't the condition be
Item 2 isn't a good option: a broken build system just give the user a
very bad impression that OS self isn't workable or stable. It's better
that we fully support Windows native or remove from the list at all.
What I means the full is that all config must pass the automation
build and run the
If my understanding is correct, the machine need donate to ASF, is that correct?
On Thu, Jan 16, 2020 at 7:25 PM Alin Jerpelea wrote:
>
> I can offer testing setup with a machine that builds daily all configs and
> exports the logs on github help us spot the issues?
>
> Alin
>
>
> On Wed, Jan
Since NuttX use Kconfig system, the simple pull/apply/compile cycle
isn't enough to catch all possible error. Actually, all my commits
pass our local automation build(four config: sim, armv7-m, armv8-m and
armv7-a) before PR sent out.
Haitao is preparing the jenkins job to run all possible config,
On Mon, Jan 13, 2020 at 8:32 AM Gregory Nutt wrote:
>
>
> >
> >> So I guess our choices are:
> >>
> >> 1. Reinstate (void) only where the warning occurs.
> >>
> >> 2. Reinstate (void) everywhere return values aren't checked. What a
> >> nightmare.
> >>
> >> 3. Change defines such as the above to
On Wed, Jan 15, 2020 at 5:54 AM Justin Mclean wrote:
>
> Hi,
>
> > The report from Haitao show that all arm 400 config can build within
> > 94min with his machine
>
> What report? Where can I find this?
>
This just our internal test,and share in Wechat, not the final report.
I shared this
On Wed, Jan 15, 2020 at 2:21 AM Gregory Nutt wrote:
>
> Hi, Xiang,
> > Since NuttX use Kconfig system, the simple pull/apply/compile cycle
> > isn't enough to catch all possible error. Actually, all my commits
> > pass our local automation build(four config: sim, armv7-m, armv8-m and
> > armv7-a)
On Wed, Jan 15, 2020 at 3:01 AM Gregory Nutt wrote:
>
>
> > Haitao is preparing the jenkins job to run all possible config, but
> > the config number is huge, we need to donate several powerful severs
> > to ensure the precheck can finish in half hour.
>
> I am repeating myself, but it is worth
Ok, I have closed it.
On Fri, Jan 10, 2020 at 10:51 AM Brennan Ashton
wrote:
> As I said we control this. I'll open the correct PR, let's not bother
> infra when it is on us.
>
> --Brennan
>
> On Thu, Jan 9, 2020, 6:43 PM Xiang Xiao wrote:
>
>> I justed ope
I justed open a JIRA for this:
https://issues.apache.org/jira/browse/INFRA-19692
Thanks
Xiang
On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt wrote:
> My preference would be to let users submit issues on github, but then
> track them with Jira. Is it possible to link Jira issues to github
All issues already provide the fix:
https://github.com/apache/incubator-nuttx-apps/pull/3
https://github.com/apache/incubator-nuttx/pull/23
Sorry, Kconfig system is too flexible to cover all combinations.
The automation build check is very impotant to ensure the change can
pass all possible
On Fri, Jan 3, 2020 at 3:10 AM Gregory Nutt wrote:
>
> Here is the summary of build test problems that I have seen. I may
> still encounter more.
>
> Question: Who is going to do the PRs for all of these? I will merge
> the PRs an retest them, but someone else needs to submit them. I have
>
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.
ll the weeds!
>
We have two options:
1.Ensure the changed/new code comply with the coding standard
2.Ensure the whole modified file comply with the coding standard
If the community like the 2nd option, I am fine.
> David
>
> -Original Message-
> From: Xiang Xiao [mailto:xiaoxiang781
Greg, please go ahead.
I don't have the time to finish the improvement right now.
On Tue, Dec 31, 2019 at 10:37 AM Gregory Nutt wrote:
>
> Hi, Xiao Xiang,
>
> I we discussed in the comments to PR 12, I did merge PR 12 onto the
> nxstyle branch. Do you plan to fix the additional things that you
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
ks
> On 12/31/2019 11:25 PM, Xiang Xiao wrote:
>
>
>
> 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 Gre
Hi Peng,
>From http://www.cplusplus.com/reference/cstdio/fwrite/
fwrite return zero to indicate the error, the detailed info could get
from errno.
So the right change is modified the error handling code in
nsh_catfile, not the return type of fwrite.
Thanks
Xiang
On Tue, Dec 24, 2019 at 9:48 AM
I definitely support this approach: keep the original workflow before
the new workflow setup.
We have enough time to achieve "THE APACHE WAY" step by step before
NuttX graduate to the top level project.
On Tue, Dec 24, 2019 at 8:51 AM Gregory Nutt wrote:
>
> Recent events have made me reconsider
Should we move GitBox email to other list like rev...@nuttx.apache.org?
Thanks
Xiang
On Tue, Dec 24, 2019 at 9:02 AM GitBox wrote:
>
> patacongo merged pull request #1: imxrt fixes
> URL: https://github.com/apache/incubator-nuttx/pull/1
>
>
>
>
>
Can we move wiki from
https://cwiki.apache.org/confluence/display/NUTTXTEST to
https://cwiki.apache.org/confluence/display/NUTTX now?
Thanks
Xiang
On Fri, Dec 20, 2019 at 4:59 PM Justin Mclean wrote:
>
> Hi,
>
> > In the past nuttx.org was just the wiki, but I see that there is a standard
> >
ization and have complete access to all repositories and teams
>
> Do ALL the PPMC agree that ALL have FULL unfetter access?
>
> David
>
>
> -Original Message-
> From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com]
> Sent: Thursday, December 26, 2019 5:39 A
After try the test website, something need to take:
1.incubator-nuttx-website.git need create to host the website self
2.NuttX JIRA database need be created
3.http://nuttx.incubator.apache.org need update
Who familiar with infra can do a favor?
Thanks
Xiang
On Thu, Dec 26, 2019 at 6:48 PM Hans
I need correct something here:
1.Haitao don't try or prepare PX4 workflow in github.com/nuttx, we
just do the workflow defined by PPMC
2.Haitao try the workflow work outside apache just because he don't
have the right
3.Any work done by Haitao even in github.com/nuttx should be reviewed
by all
Why we not reuse github.com/nuttx to do the test?
On Thu, Dec 26, 2019 at 9:31 PM Haitao Liu wrote:
>
> David, my github username liuguo09 liugu...@gmail.com. We could do some
> tests to prepare for final workflow.
>
> David Sidrane 于2019年12月26日周四 下午4:55写道：
>
> > Hi Haitao,
> >
> > I can add
at 9:40 PM David Sidrane wrote:
>
> The PPMC does not have admin on it
>
> -Original Message-----
> From: Xiang Xiao [mailto:xiaoxiang781...@gmail.com]
> Sent: Thursday, December 26, 2019 5:39 AM
> To: dev@nuttx.apache.org
> Subject: Re: Workflow Development
>
> Why
Thanks for your help, Justin.
On Fri, Dec 27, 2019 at 5:45 AM Justin Mclean wrote:
>
> Hi,
>
> I’m not your only mentor, other mentors can help you here and if mentors are
> not available the PPMC can (in general) request Infra to set things up.
>
> > 1.incubator-nuttx-website.git need create
On Fri, Dec 27, 2019 at 5:21 AM Justin Mclean wrote:
>
> Hi,
>
> > I can add you as an Admin to this organization
> > https://github.com/nuttx-to-asf it sole purpose is uninhibited collaboration
> > to feed upstream.
>
> I would recommend not to work outside of the ASF repos, moving that to the
On Wed, Dec 25, 2019 at 6:52 AM Gregory Nutt wrote:
>
>
> > If they are related / dependent on each other, then I think those
> > kinds of patchsets should be encapsulated in one branch.
>
> The need to be applied and committed in sequence. Sometimes the final
> patch is the one that fixes the
Yes, I agree that we shouldn't make the workflow too hard to scare
people for contribution.
NuttX isn't a new project, it's open source for more than ten years
and has a mature workflow, the whole community is already familiar
with it.
Let me summary the current workflow:
1.User send patch against
a patch fix it, please take a look:
https://github.com/apache/incubator-nuttx-website/pull/2
>
>
> Xiang Xiao 于2019年12月27日周五 下午4:59写道：
>
> > https://git-wip-us.apache.org/repos/asf?p=incubator-nuttx.git
> > It's better to change the description from "Apache nuttx" to
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:
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
rom Gitbox.
>
> Once we are all set up and ready to receive patches/PRs, we may run
> into the same issue.
>
>
> On Thu, Dec 26, 2019 at 1:34 PM Xiang Xiao wrote:
> >
> > The dev list traffic may reduce after we finish the workflow discussion.
> > but email fr
gt; > 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 and github account here?
> > > >
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
reading some projects' board reports, I came across this:
> > >
> > >> Gitbox traffic is now going to issues@. The community was losing dev@
> > >> subscribers because of the high volume of traffic from Gitbox.
> > >
> > > Once we are all set up
---
> >
> > Key: INFRA-19645
> > URL: https://issues.apache.org/jira/browse/INFRA-19645
> > Project: Infrastructure
> > Issue Type: Task
> > Components: Mailing Lists
> >Reporter: Xian
But, I think that the user who hasn't an apache account can't create
an issue in JIRA.
On Sun, Jan 5, 2020 at 10:51 AM Gregory Nutt wrote:
>
>
> >>> Maybe people should not file a bug for hardware-specific issues that
> >>> affect only their specific configuration. As you point out, it is
> >>>
On Mon, Jan 6, 2020 at 5:02 AM Gregory Nutt wrote:
>
>
> > Something strange is happening with the git repositories.
> >
> > Several times recently, I have seen things inexplicably disappear and
> > reappear.
>
> You had me going with that. The answer is that the order of the commits
> is not
Guiding doesn't have the free time to finish netlink crypto in the
near future. It's fine to delete the branch now.
Thanks
Xiang
On Mon, Jan 6, 2020 at 3:11 AM Gregory Nutt wrote:
>
> Hi, Xiao Xiand and Guiding Li,
>
> I created the netlink_crypto branch several months back to help you
>
https://github.com/apache/incubator-nuttx/pull/47
checkpatch.sh is ready, you can invoke it like this:
tools/checkpatch.sh -p patch-list
tools/checkpatch.sh -c commit-list
tools/checkpatch.sh -f file-list
The first two just check the modified portion, the last one check the
whole content.
And with
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:
> https://githu
1 - 100 of 523 matches
Mail list logo
