I'm getting cranky in my old age. Aplogies. 

Just don't have time for PC.
—
Dave Carlton
da...@polymicro.net <mailto:da...@polymicro.net>




> On Dec 2, 2020, at 14:56, John Benediktsson <mrj...@gmail.com 
> <mailto:mrj...@gmail.com>> wrote:
> 
> Hi Dave,
> 
> I really don't disagree with you that much, however there is likely going to 
> be an increasing shift to main over the next few years, here's some 
> background by GitHub on the topic:
> 
>     https://github.com/github/renaming <https://github.com/github/renaming>
> 
> And some information about the change to support init.defaultBranch in git 
> 2.28:
> 
>     https://github.blog/2020-07-27-highlights-from-git-2-28/ 
> <https://github.blog/2020-07-27-highlights-from-git-2-28/>
> 
> There is no need to rush into a rename... If anyone feels strongly, we can 
> even delay it or discuss it further.  Ideally, it won't impact anyone except 
> the core developers since we can maintain a master branch that mirrors main 
> (rather than the other way around) if we commit to the rename at some point.  
> In addition, "fixing" other language uses like whitelist/blacklist to 
> allowlist/blocklist is pretty much a resolved topic for most projects, 
> whether they've had direct feedback about offensive language or not.
> 
> I wonder when it's not going to be PC to refer to algorithms like STONITH.
> 
> Best,
> John.
> 
> 
> 
> 
> 
> On Wed, Dec 2, 2020 at 12:38 PM Dave Carlton <da...@polymicro.net 
> <mailto:da...@polymicro.net>> wrote:
> 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 <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

_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to