Re: [incubator-nuttx] branch master updated (499607d -> 3b311ab)

2020-02-07 Thread Abdelatif Guettouche
> It looks like when you do a merge commit a different message is > displayed. I couldn't find a "non merge commit" for your username. That has nothing to do with merge commits. Pushed are not all displayed in the same way, I don't know why. But I don't think there is something wrong with the mirr

Re: [incubator-nuttx] branch master updated (499607d -> 3b311ab)

2020-02-07 Thread Abdelatif Guettouche
> from 499607d S32K add support for Nxp drone boards (#224) > add 3b311ab tools/testbuild.sh: use function to call make and fail > handle in common I think you should read it as: From _your_ commit, I added a commit. You can see from the git history that that's the case. You can see the

RE: [incubator-nuttx] branch master updated (499607d -> 3b311ab)

2020-02-07 Thread David Sidrane
What's the issue, guys? The issue is Confusion! If I did the merge of the PR on github, why did it say you do the push? aguettouche pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git > from 499607d S32K add support for Nxp drone boards (#2

Re: Podling Nuttx Report Reminder - February 2020

2020-02-07 Thread Justin Mclean
Hi, > I personally deliberately avoided number of commits/PRs in the report > as I saw Justin giving the same remark in his review to other reports > that did that, and I believe he has a good argument. I’s not just my point, the board frequently gives the same feedback on reports that just cont

Re: [incubator-nuttx] branch master updated (499607d -> 3b311ab)

2020-02-07 Thread Abdelatif Guettouche
What's the issue, guys? We've already talked about which one is a mirror of the other. Here what Justin had to say. > The gitbox is the primary repo and any change to it are synced to GitHub. > Also any changes to GitHub are synced to GitBox. > > If thing do get out of sync (it sometimes but rar

[GitHub] [incubator-nuttx-testing] xiaoxiang781216 merged pull request #6: Get the full directory name of the cibuild.sh no matter where called …

2020-02-07 Thread GitBox
xiaoxiang781216 merged pull request #6: Get the full directory name of the cibuild.sh no matter where called … URL: https://github.com/apache/incubator-nuttx-testing/pull/6 This is an automated message from the Apache Git Se

[GitHub] [incubator-nuttx-testing] liuguo09 opened a new pull request #6: Get the full directory name of the cibuild.sh no matter where called …

2020-02-07 Thread GitBox
liuguo09 opened a new pull request #6: Get the full directory name of the cibuild.sh no matter where called … URL: https://github.com/apache/incubator-nuttx-testing/pull/6 …from Or it would fail to set nuttx/apps/tools/prebuilt dirs correctly when cibuild.sh is not called by 'cd

[GitHub] [incubator-nuttx-testing] xiaoxiang781216 merged pull request #5: Call testbuild.sh with -x option to set it fail fast for check build …

2020-02-07 Thread GitBox
xiaoxiang781216 merged pull request #5: Call testbuild.sh with -x option to set it fail fast for check build … URL: https://github.com/apache/incubator-nuttx-testing/pull/5 This is an automated message from the Apache Git Se

RE: [incubator-nuttx] branch master updated (499607d -> 3b311ab)

2020-02-07 Thread Xiang Xiao
Yes, I also confuse. How apache mirror get updated? -Original Message- From: David Sidrane Sent: 2020年2月7日 22:58 To: dev@nuttx.apache.org Subject: RE: [incubator-nuttx] branch master updated (499607d -> 3b311ab) Why do I see these commits that say "aguettouche pushed a change to branch

RE: [incubator-nuttx] branch master updated (499607d -> 3b311ab)

2020-02-07 Thread David Sidrane
Why do I see these commits that say "aguettouche pushed a change to branch master" I thought that commits to github or apache are just mirrored? It is supposed to be automatic? -Original Message- From: aguettou...@apache.org [mailto:aguettou...@apache.org] Sent: Friday, February 07, 2020

[GitHub] [incubator-nuttx-testing] maht commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build …

2020-02-07 Thread GitBox
maht commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build … URL: https://github.com/apache/incubator-nuttx-testing/pull/5#issuecomment-583416500 it looks good ok to me This is an automa

[GitHub] [incubator-nuttx-testing] liuguo09 commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build …

2020-02-07 Thread GitBox
liuguo09 commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build … URL: https://github.com/apache/incubator-nuttx-testing/pull/5#issuecomment-583400349 Thanks. @maht @xiaoxiang781216 could you help review and merge if ok. ---

Re: Podling Nuttx Report Reminder - February 2020

2020-02-07 Thread Abdelatif Guettouche
Hi, I personally deliberately avoided number of commits/PRs in the report as I saw Justin giving the same remark in his review to other reports that did that, and I believe he has a good argument. Probably a better stats would be number of PRs from new contributors, that will show that the projec

[GitHub] [incubator-nuttx-testing] Ouss4 commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build …

2020-02-07 Thread GitBox
Ouss4 commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build … URL: https://github.com/apache/incubator-nuttx-testing/pull/5#issuecomment-583382478 Hi @liuguo09 apache/incubator-nuttx#221 was merged.

Re: Podling Nuttx Report Reminder - February 2020

2020-02-07 Thread Flavio Junqueira
+1 to more metrics about community, code changes, etc. I have signed off in any case. -Flavio > On 6 Feb 2020, at 03:27, Justin Mclean wrote: > > HI, > >> Instead of giving absolute numbers, why not say there was an increase of x% >> in the number of PRs applied, etc > > Which is slightly be

[GitHub] [incubator-nuttx-testing] liuguo09 commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build …

2020-02-07 Thread GitBox
liuguo09 commented on issue #5: Call testbuild.sh with -x option to set it fail fast for check build … URL: https://github.com/apache/incubator-nuttx-testing/pull/5#issuecomment-583279728 This change also depends on https://github.com/apache/incubator-nuttx/pull/221.

[GitHub] [incubator-nuttx-testing] liuguo09 opened a new pull request #5: Call testbuild.sh with -x option to set it fail fast for check build …

2020-02-07 Thread GitBox
liuguo09 opened a new pull request #5: Call testbuild.sh with -x option to set it fail fast for check build … URL: https://github.com/apache/incubator-nuttx-testing/pull/5 …error For PR check build, call testbuild.sh with -x option to set it fail fast if build error occured. Note

[GitHub] [incubator-nuttx-testing] liuguo09 commented on issue #2: Multibranch pipeline job example

2020-02-07 Thread GitBox
liuguo09 commented on issue #2: Multibranch pipeline job example URL: https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-583278543 > @davids5 I have not tested in builds.apache.org Jenkins, since I have no rights to create the pipeline job. I tested it on an external Jen