+1 

And the patch is the same format and put on this mail address just like when we 
were in the Google Group? 

Verstuurd vanaf mijn iPhone

> Op 21 dec. 2019 om 12:30 heeft Xiang Xiao <xiaoxiang781...@gmail.com> het 
> volgende geschreven:
> 
> 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.
> These random named and created branches just confuse people who clone the 
> repo.
> 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

Reply via email to