for another bug tracker we use github and all issued are created on a
template.
This template can start with the following title "git name - board /
component - version - issue".
Such layout eases the sorting and people can easy spot if there is
something similar to theyr issue.
On Mon, Dec 3
xiaoxiang781216 opened a new 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
…or directory
Make builtin_list.c instead of builtin_list.o depend on builtin_proto.h and
builtin_proto.c
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361978161
##
File path: tools/README.txt
##
@@ -313,7 +313,15 @@ nxstyle.c
standard. This program is completely ig
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361979138
##
File path: tools/nxstyle.c
##
@@ -1896,24 +1962,32 @@ int main(int argc, char **argv, char **envp)
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361979048
##
File path: tools/nxstyle.c
##
@@ -1896,24 +1962,32 @@ int main(int argc, char **argv, char **envp)
davids5 commented on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569671947
@xiaoxiang781216 - all review Items have been addressed - Please merge or
ask an other PPMC to merge it.
-
+1 for using github
I have used both - I am more failure with github then Jira capabilities.
Jira for me was very slow.
So if there is a Jira PRO on the team and they can automate Github PR/Issue
tracking and syncing/closing into Jira that would be the way to go.
The benefit is that d
masayuki2009 opened a new pull request #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16
**Summary**
- Added initial support for Sipeed Maix Bit board with Kendryte K210
processor.
- K210 has two RV64GC cores but in this PR only the primary core is enabled.
How do we stop this from happening? It is not fare to our "Customers"
This certainly is of NO HELP Roman Zhukov [nore...@bitbucket.org]
How can we warn him?
Greg, Can you see hi email and warn him?
David
*From:* Roman Zhukov [mailto:nore...@bitbucket.org]
*Sent:* Monday, December 30,
Lots of Jira tutorials. Not knowing how to use it does not not sound
like a strong argument against it:
Quick Google:
https://www.guru99.com/jira-tutorial-a-complete-guide-for-beginners.html
https://www.atlassian.com/agile/tutorials
https://www.atlassian.com/software/jira/guides/getting-star
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361990500
##
File path: tools/nxstyle.c
##
@@ -43,53 +43,128 @@
#include
#include
#include
+#include
+#
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361986470
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361987147
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361991442
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361989296
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361990957
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361989974
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r361988441
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
New JIRA request INFRA create iss...@nuttx.apache.org:
https://issues.apache.org/jira/browse/INFRA-19645
On Sat, Dec 28, 2019 at 3:24 AM Alin Jerpelea wrote:
>
> 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 Ala
patacongo commented on a change in pull request #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16#discussion_r362002179
##
File path: include/stdint.h
##
@@ -273,8 +273,13 @@ typedef _uint64_t uint_fast64_t;
/* Integer types capable of ho
patacongo commented on a change in pull request #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16#discussion_r362002179
##
File path: include/stdint.h
##
@@ -273,8 +273,13 @@ typedef _uint64_t uint_fast64_t;
/* Integer types capable of ho
patacongo commented on a change in pull request #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16#discussion_r362002179
##
File path: include/stdint.h
##
@@ -273,8 +273,13 @@ typedef _uint64_t uint_fast64_t;
/* Integer types capable of ho
patacongo commented on a change in pull request #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16#discussion_r362002179
##
File path: include/stdint.h
##
@@ -273,8 +273,13 @@ typedef _uint64_t uint_fast64_t;
/* Integer types capable of ho
patacongo commented on a change in pull request #12: nxstyle improvements with
No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362005445
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362007291
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362007238
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362007489
##
File path: tools/nxstyle.c
##
@@ -43,53 +43,128 @@
#include
#include
#include
+#include
+#include
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362007456
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362007559
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362007745
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362010142
##
File path: tools/README.txt
##
@@ -313,7 +313,15 @@ nxstyle.c
standard. This program is compl
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362010914
##
File path: tools/nxstyle.c
##
@@ -134,70 +211,80 @@ int main(int argc, char **argv, char **envp)
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362011999
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362011203
##
File path: tools/nxstyle.c
##
@@ -134,70 +211,80 @@ int main(int argc, char **argv, char **envp)
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362011922
##
File path: tools/nxstyle.c
##
@@ -135,67 +211,98 @@ int main(int argc, char **argv, char **envp)
int e
davids5 commented on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-56970
@xiaoxiang781216 - thank you for a through review and all the value added
suggestions.
I am done, all the changes: I added a version in th
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362014598
##
File path: tools/nxstyle.c
##
@@ -134,70 +211,80 @@ int main(int argc, char **argv, char **envp)
int r
[moved from priv...@nuttx.apache.org]
Hi, Xiao Xiang and Haitao Liu
Haitao is preparing a script for style check, the feature include:
1.Auto build nxstyle
2.Improve nxstyle to check the partial file for supporting patch like file
3.Input can be the source files, patch file or commit id
I men
On Mon, Dec 30, 2019 at 11:05 PM David Sidrane wrote:
>
> >Haitao is preparing a script for style check, the feature include:
> >1.Auto build nxstyle
>
> 2.Improve nxstyle to check the partial file for supporting patch like file
>
> Are you saying only check the files changed?
>
Yes, I mean that
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362017755
##
File path: tools/nxstyle.c
##
@@ -386,24 +467,26 @@ int main(int argc, char **argv, char **envp)
My experience with Jira is that it is powerful if you know how to use it,
but that it can be really clumsy and difficult to learn. There's also a lot
of pain with certain actions, like switching issue types in bulk and things
like that.
Github on the other hand is much more straightforward and sim
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362020988
##
File path: tools/nxstyle.c
##
@@ -134,70 +213,78 @@ int main(int argc, char **argv, char **envp)
xiaoxiang781216 commented on a change in pull request #12: nxstyle improvements
with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362020748
##
File path: tools/nxstyle.c
##
@@ -669,25 +757,25 @@ int main(int argc, char **argv, char **envp)
Mentor,
Please help to create iss...@nuttx.apache.org and redirect GitBox email to it.
On Mon, Dec 30, 2019 at 11:21 PM Daniel Gruno (Jira) wrote:
>
>
> [
> https://issues.apache.org/jira/browse/INFRA-19645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Daniel Gr
I'm a little torn on this one, but I'd say Github wins for me.
Are they mutually exclusive?
+1 for github
On Mon, Dec 30, 2019, 18:32 Gregory Nutt wrote:
> > I'm a little torn on this one, but I'd say Github wins for me.
> Are they mutually exclusive?
>
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362035777
##
File path: tools/nxstyle.c
##
@@ -669,25 +757,25 @@ int main(int argc, char **argv, char **envp)
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362035720
##
File path: tools/nxstyle.c
##
@@ -386,24 +467,26 @@ int main(int argc, char **argv, char **envp)
davids5 commented on a change in pull request #12: nxstyle improvements with No
tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#discussion_r362035976
##
File path: tools/nxstyle.c
##
@@ -134,70 +213,78 @@ int main(int argc, char **argv, char **envp)
int r
davids5 commented on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569731061
@xiaoxiang781216
The program needs many more functional changes to be useful, My vacation is
coming to an end.
I will not be inv
Can people who are advocating for GitHub address the two main points that I
had made. The second one I really don't see a workaround for. To be clear
if we can get around both of these I'm happy to be on the GitHub train.
1) Multiple repos. We might have an issue or feature the spans the os,
ap
patacongo commented on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569743134
@xiaoxiang781216 Perhaps you should merge this onto a development branch.
Where we can work together to continue development. It is currentl
patacongo edited a comment on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569743134
@xiaoxiang781216 Perhaps you should merge this onto a features branch,
perhaps called 'nxstyle'. There we can work together to continu
+1 for github
There has been no formal [VOTE] started. Any formal vote must be
preceded by a [DISCUSS] so that we can all understand the issues and we
can all be qualified to vote.
It is probably too early to start a discussion or vote since we have not
eventthe vaguest plan in place fo
patacongo edited a comment on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569743134
@xiaoxiang781216 Perhaps you should merge this onto a feature branch,
perhaps called 'nxstyle'. There we can work together to continue
Hi Brenan,
See Below.
-Original Message-
From: Brennan Ashton [mailto:bash...@brennanashton.com]
Sent: Monday, December 30, 2019 8:52 AM
To: dev@nuttx.apache.org
Subject: Re: Issue Reporting
Can people who are advocating for GitHub address the two main points that I
had made. The
xiaoxiang781216 commented on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569756871
@patacongo, @davids5 fix resolve my most comment except snprintf, but that
is a very minor issue. The patch is good for me, you can squa
patacongo merged pull request #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on
patacongo commented on issue #12: nxstyle improvements with No tooling
URL: https://github.com/apache/incubator-nuttx/pull/12#issuecomment-569758903
@xiaoxiang781216 Please, make whatever additional changes to you want to
make against branch nxstyle and merge that branch to master.
---
Hi,
Did anyone try to move the website to Apache?
It looks like Xiao ticket [1] got an answer.
If not, what was the hold up?
I need that piece of information to put it in the January report.
1. (https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-19634)
On Fri, Dec 27, 2019 at 5:2
Hi,
Just an observation. You seem to making decisions based and what you think will
happen rather than what actually will happening and ignoring advice given.
While these things can be corrected, splitting the community so early is not
recommended. Did anyone read the links to the conversations
I was skimming https://www.apache.org/foundation/marks/ and I see
several things that might have impact in the future.
First, there is the *What is the "confusing similarity" or "likelihood
of confusion" test? *Certainly the versions of NuttX destributed in the
Motorola MDK and Google Ara unde
I was skimming https://www.apache.org/foundation/marks/ and I see
several things that might have impact in the future.
First, there is the *What is the "confusing similarity" or "likelihood
of confusion" test? *Certainly the versions of NuttX destributed in
the Motorola MDK and Google Ara un
Hi Justin,
The discussion has shifted more towards redirecting gitbox
notifications to their own mailing list.
Something similar to commit@
We are just concerned that this may cause a lot of noise in dev@
On Mon, Dec 30, 2019 at 9:21 PM Justin Mclean wrote:
>
> Hi,
>
> Just an observation. You s
Hi,
> The discussion has shifted more towards redirecting gitbox
Which splits the community. How many people will subscribe to that list? Will
user get answers to their questions if less (or no) people see them?
> We are just concerned that this may cause a lot of noise in dev@
So why decide i
Nope!
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Monday, December 30, 2019 1:43 PM
To: dev@nuttx.apache.org
Subject: Re: Future Trademark Issues
> I was skimming https://www.apache.org/foundation/marks/ and I see
> several things that might have impact in th
Hold on!
Having a coding standard with 4000+ files in the repo that do not pass the
test…
…reminds me of this great line…
"This is the problem with issuing purity tests you cannot yourself pass"
Clear, Consistent, Standardized Coding Style
Taking a quick look at PX4 it looks like it would be an issue, however it's
one that easily fixed in a number of ways. It's not urgent to fix now.
On Tue, 31 Dec 2019, 09:57 David Sidrane, wrote:
> Nope!
>
> -Original Message-
> From: Gregory Nutt [mailto:spudan...@gmail.com]
> Sent: Mon
Hi, Justin
I think we will just let the gitbox forwarded emails to go to another
mailing list, which we can see on GitHub? No information lost.
And the problem is, actually we are answering the questions on GitHub but
then the answer is sent to this mailing list again with a hard to read
format..
Hi,
I think we will just let the gitbox forwarded emails to go to another
> mailing list, which we can see on GitHub? No information lost.
>
Which assumes you use github and not every one does. New users may not,
again try to put yourself in a user shoes not a committer on the project.
What's con
On Tue, Dec 31, 2019 at 7:09 AM David Sidrane wrote:
>
> Hold on!
> Having a coding standard with 4000+ files in the repo that do not pass the
> test…
> …reminds me of this great line…
> "This is the problem with issuing purity tests you cannot yourself pass"
> Clear, Consistent, Standardized Codi
masayuki2009 commented on a change in pull request #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16#discussion_r362137425
##
File path: include/stdint.h
##
@@ -273,8 +273,13 @@ typedef _uint64_t uint_fast64_t;
/* Integer types capable of
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
mentioned in the PR comments? Or should I go ahead and merge the PR to
master and call it done?
I do have some functional improvements that
Review comment:
@patacongo Thanks for the comment. I understand what I should do. I'll fix
the commits and force to push again.
No rush. PRs are stuck in the process now. We (actually Nathan) had
just started the Workflow requirements when the holidays hit us and
brought everything
On Mon, Dec 30, 2019 at 9:00 PM Xiang Xiao
wrote:
>
> 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.
I can think of one disadvantage to #2:
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.
I can tell you how I did this in the past as the single committer. In
the last year or so, nxs
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
>
masayuki2009 commented on issue #16: feature k210
URL: https://github.com/apache/incubator-nuttx/pull/16#issuecomment-569855598
@patacongo I fixed what you pointed out and pushed again.
This is an automated message from the Ap
Greg, please go ahead.
I don't have the time to finish the improvement right now.
Done!
On Mon, Dec 30, 2019 at 9:42 PM Gregory Nutt wrote:
> > Review comment:
> > @patacongo Thanks for the comment. I understand what I should do. I'll
> > fix the commits and force to push again.
>
> No rush. PRs are stuck in the process now. We (actually Nathan) had
> just started the Workfl
I seemed to have dropped off the face of the earth for a few days
because of overtime to get some projects shipped. But I did not
forget. I'm working on it now.
Sorry... didn't mean to rush you. If you can get a little more
framework with some inline writing instructions or whatever, then I
adamfeuer commented on issue #13: sama3 sam_serial.c USART selection fixes
URL: https://github.com/apache/incubator-nuttx/pull/13#issuecomment-569866163
@patacongo Is there anything else fix in this PR before it can be merged?
On Mon, Dec 30, 2019 at 11:32 PM Gregory Nutt wrote:
> > I seemed to have dropped off the face of the earth for a few days
> > because of overtime to get some projects shipped. But I did not
> > forget. I'm working on it now.
>
> Sorry... didn't mean to rush you. If you can get a little more
> fr
But I think posting so many 'hard to read' emails to the mailing list will
hurt user experience and cause users to leave...
Actually for a committer, or a long term contributor who is familiar with
the community, he/she can just use a filter to filter these emails out,
this is what I have done for
For me I suggest we start with GitHub issues.
For problem #1, the cross repo PRs, I think it is fine to have only one
issue in the main repo? We can reference multiple PRs in an issue and the
PRs could come from other repos.
And for problem #2, once the user sends the patch to this mailing list,
85 matches
Mail list logo
