Re: Git master/main/trunk/current/best...

On 6/10/2022 6:14 am, Sebastian Huber wrote: > On 05/10/2022 20:37, Joel Sherrill wrote: >> On Thu, Sep 29, 2022 at 4:24 PM Chris Johns > > wrote: >> >>     On 30/9/22 4:00 am, Joel Sherrill wrote: >> > I'd like to propose that short term we change lwip main to master

Re: Git master/main/trunk/current/best...

On 05/10/2022 20:37, Joel Sherrill wrote: On Thu, Sep 29, 2022 at 4:24 PM Chris Johns > wrote: On 30/9/22 4:00 am, Joel Sherrill wrote: > I'd like to propose that short term we change lwip main to master for > consistency with existing repos. This helps

Re: Git master/main/trunk/current/best...

On Thu, Sep 29, 2022 at 4:24 PM Chris Johns wrote: > On 30/9/22 4:00 am, Joel Sherrill wrote: > > I'd like to propose that short term we change lwip main to master for > > consistency with existing repos. This helps avoid stupid mistakes > because lwip > > is the odd case. > > I propose we use de

Re: Git master/main/trunk/current/best...

On 30/9/22 4:00 am, Joel Sherrill wrote: > I'd like to propose that short term we change lwip main to master for > consistency with existing repos. This helps avoid stupid mistakes because lwip > is the odd case. I propose we use devel. I prefer it over main. When should we change away from maste

Git master/main/trunk/current/best...

Hi I've been bitten twice no because lwip uses main instead of master. Although I am not offended by having the trunk be named master, I understand others do care. I'd like to propose that short term we change lwip main to master for consistency with existing repos. This helps avoid stupid mistak