search

PRUNERS / FLiT

A project to quickly detect discrepancies in floating point computation across hardware, compilers, libraries and software.
Other
36 stars 6 forks source link

Replace `master` with `main` #329

Open mikebentley15 opened 4 years ago

mikebentley15 commented 4 years ago

Bug Report

Description

We would like to replace the master branch to main. This allows us to abandon "master" vocabulary which reminds some of a master-slave relationship.

If there are any changes to make in the files of the repository, it will need to be done for all branches.

IanBriggs commented 4 years ago

If we are changing naming, my two cents is that since we have “branches” the biggest one should be the trunk. Thoughts?

mikebentley15 commented 4 years ago

Or "stable"

On Sat, Jul 11, 2020, 23:10 Ian Briggs notifications@github.com wrote:

If we are changing naming, my two cents is that since we have “branches” the biggest one should be the trunk. Thoughts?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/PRUNERS/FLiT/issues/329#issuecomment-657176117, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACBVGNEOVYCB4T6CIRX77P3R3FASRANCNFSM4OXP6SJA .

mikebentley15 commented 4 years ago

I'm rethinking using main because it is actually not our main development branch. That title goes to the devel branch.

You suggested trunk to go back to SVN days and the idea that all branches come out of this one. That's not accurate in our case either, since we branch from devel.

@IanBriggs What did you think of my suggestion to using stable instead of main or master? Our old master branch is intended to have only the stable releases of the software. I think stable or latest-release would better describe what it represents.

Thoughts?