Email list hosting service & mailing list manager

main vs master branch Lassi Kortela (06 Nov 2022 22:26 UTC)
Re: main vs master branch Arthur A. Gleckler (06 Nov 2022 22:35 UTC)
Re: main vs master branch Lassi Kortela (06 Nov 2022 22:44 UTC)
Re: main vs master branch siiky (06 Nov 2022 22:51 UTC)
Re: main vs master branch Arthur A. Gleckler (06 Nov 2022 23:41 UTC)
Re: main vs master branch Jeremy Steward (07 Nov 2022 06:31 UTC)
Re: main vs master branch Lassi Kortela (07 Nov 2022 09:00 UTC)
Re: main vs master branch Marc Nieper-Wißkirchen (07 Nov 2022 06:47 UTC)
Re: main vs master branch siiky (06 Nov 2022 22:47 UTC)

Re: main vs master branch Marc Nieper-Wißkirchen 07 Nov 2022 06:47 UTC

On the one hand side, I found the master/main discussion superficial,
needless, and detrimental; on the other hand, I couldn't care less
about the name of the default branch.  So I usually took whatever my
tool at hand suggested as its default.  So when it comes to SRFI 230
and SRFI 237 blame it on me.

Am So., 6. Nov. 2022 um 23:35 Uhr schrieb Arthur A. Gleckler
<xxxxxx@speechcode.com>:
>
> On Sun, Nov 6, 2022 at 2:26 PM Lassi Kortela <xxxxxx@lassi.io> wrote:
>>
>> The use of "main" as the default branch in some recent SRFIs (at least
>> 234, 235, 237) breaks tools that assume "master" branch. Currently at
>> least the `srfi clone` command is affected.
>>
>> Could we use the same branch name as for the other 200+ SRFIs?
>
> For one reason or another, SRFIs 217, 224, 230, 232, 233, 234, 235, 237 use main. Those may have been accidents on my part, or because I started with someone else's repo. The rest use master. To try to create some consistency, I've already set my defaults so that master is used when I create a Git repo for a SRFI from scratch.
>
> However, it should be easy to make our tools work around what inconsistency we have.