I see no reason to change existing project to use this stupid convention. If you want to use main for new projects, fine, but why take time and effort to fit into a new PC paradyme is asinine. Whats this world ocming to? master/slave, master/client in context of CS in no way reflects upon slavery in the south IMHO. Put on your big guy shorts or big girl panties as the case may be and get on with your life, its too short for this kind of PC shite.
</rant> — Dave Carlton da...@polymicro.net <mailto:da...@polymicro.net> > On Dec 2, 2020, at 10:30, Zoltán Kéri via Factor-talk > <factor-talk@lists.sourceforge.net > <mailto:factor-talk@lists.sourceforge.net>> wrote: > > Dear Lord, I am so sorry that this is a thing today. The main reason for the > change is the word's ties to slavery, except the term within this context has > absolutely nothing to do with slavery. It is a bullshit move from whoever > keeps pushing it, they have zero context-awareness. Welp. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Wednesday, December 2, 2020 4:53 PM, Benjamin Pollack > <benja...@bitquabit.com <mailto:benja...@bitquabit.com>> wrote: > >> I noticed that we've got both main and master branches at this point. Should >> I be pushing to main or to master? Do we have a workflow, or we're just >> keeping them in sync for now? >> >> Factor-talk mailing list >> Factor-talk@lists.sourceforge.net <mailto:Factor-talk@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/factor-talk >> <https://lists.sourceforge.net/lists/listinfo/factor-talk> > > > > > _______________________________________________ > Factor-talk mailing list > Factor-talk@lists.sourceforge.net <mailto:Factor-talk@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/factor-talk > <https://lists.sourceforge.net/lists/listinfo/factor-talk>
_______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
