I'm not opposed to doing this. Most other projects have also done it, so it would be inline with that. It also has the advantage that "main" is a much clearer term to newbies than "master".
But note that this is not a trivial thing to do, which is why it hasn't happened yet. It's not as simple as just renaming the branch. We also have to fix all the references to "master" everywhere, including making sure that all our automation and release scripts still work. There's also an unfortunate downside of doing this, which is that anyone who already has a clone of the repo and is using "git checkout master; git pull" will have their workflows broken when master stops being updated. I don't know if there's a clean way we can do anything about that. Aaron Meurer On Mon, Jul 17, 2023 at 9:25 PM Sangyub Lee <[email protected]> wrote: > > I think that github decided to do that in 2020. > And the main reason to do this is that 'master' is agreed to be politically > offensive terminology: > > Rename offensive terminology (master) - Simon Pieters (kernel.org) > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/8037a96f-4d4c-48ca-9139-56bec7f5217en%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2BXo0N89GQb%2BzHHjCSW%3DA-gkmMsnDEOi0ene7r%3DfOXBhQ%40mail.gmail.com.
