Opps That would be me. I am sorry I just saw this when I was sending the PR and the URL of the patch to the list.
I am happy to delete the branch and the PR if you like or we can use it to explore our new environment just let me know. (Or any PPMC can deleted it or push the merge button (choose from the green drop down)) However the changes to the IMXrt are critical so please insure the patch get applied/ more below On 2019/12/21 11:30:27, Xiang Xiao <xiaoxiang781...@gmail.com> wrote: > 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 that PMC member is starting to create the branch in the > offical repo as they see the needed. > If we don't control this situation, we will have dozen(even hundred) > of branches in the offical repo soon. That is a good thing it means a project is health and being worked on but you right that the chaos has to be controlled. PR branches are (hopefully) very short lived as they are deleted when committed and discernible as a PR on github. If we adopt the naming conventions of using pr in the branch name then the fact it is a PR is self referential in nay context command line/web/tablet > These random named and created branches just confuse people who clone the > repo. I agree with is in part, naming as in the OS is key 'master_imxrt' is too master_imxrt `stage` is too vague `master-pr-imxrt_imxrt_fixes` - Says what it is: A PR against the branch master that fixes the imxrt. master has always been master in the context of nuttx and as well on gitub as the default branch. > It's important to keep the original workflow and ensure all patches > reviewed and committed by Greg before the automation tool is ready. > > Thanks > Xiang > > > On Sat, Dec 21, 2019 at 5:59 AM Alan Carvalho de Assis > <acas...@gmail.com> wrote: > > > > Hi Guys, > > > > We you can see the new repository is working fine. > > > > I submitted the i2C driver for STM32G070/NUCLEO-G070RB that was added > > to bitbucket. > > > > As a rules of thumb, please don't commit directly to the "master". > > > > I created a brash called "stage" that we could use before merging in > > to "master", this way other will have the chance to review. > > > > BR, > > > > Alan >
