Greg,
On a tangental note, what will become of our remaining repos: buildroot I’m preparing a PR to upgrade binutils and gcc! Can you still accept updates on Bitbucket? tools nxwidgets Regards, -david > On Dec 20, 2019, at 2:24 PM, Gregory Nutt <spudan...@gmail.com> wrote: > > [Cross posting to both the (deprecated) Google Group and to the Apache dev > list.] > > This is to inform all users of and contributors to NuttX that there are > changes on the way; Some things will need be done differently beginning as > of now. The Apache NuttX repositories are online and are now the master, > golden source of NuttX code. The Bitbucket nuttx/ and aps/ repositories are > now reduced to (effectively) read-only mirrors of the Apache repositories. > The new Apache NuttX repositories are located here: > > * https://github.com/apache/incubator-nuttx > * https://github.com/apache/incubator-nuttx-apps > > And also here (but not for contributions): > > * https://gitbox.apache.org/repos/asf?p=incubator-nuttx.git > * https://gitbox.apache.org/repos/asf?p=incubator-nuttx-apps.git > > NuttX users may continue to use the Bitbucket repositories with no break your > work flow. Things will change for NuttX contributors, however. The way in > which you can submit changes to NuttX repositories is different effective > immediately: > > 1. PRs against the Bitbucket repositories can no longer be accepted. > The Bitbucket repositories are functionally now read-only mirrors of > the Apache repositories. If you wish to use pull requests, you must > submit them against the https://github.com/apache/ repositories. > 2. All patches must be sent via the dev@nuttx.apache.org email. Email > sent to the Google group may be lost (although I will make some weak > effort to forward patches to dev@nuttx.apache.org). Your best bet of > not losing your changes is to submit them directly to > dev@nuttx.apache.org. You can subscribe to that list by sending an > email to dev-subscr...@nuttx.apache.org > > At present, we will be operating just as we have in the past, except using > the ASF Github repositories. We don't yet have an agreed upon workflow > requirements. Hopefully that will come soon and, when it does, there will > most certainly be some additional changes to the above submission rules. > > Greg > >
