Displaying 10 results from an estimated 10 matches for "2fjf".
Did you mean:
2f8f
2020 Jun 19
2
Inclusive language in LLVM: can we rename `master` branch?
...t; convention to name our development branch. On SVN it used to be just "trunk".
This naming is unfortunate<https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as it can hurt some contributors<https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>, and there is really no technical advantage that I know of to favor this convention over another.
I am perfectly aware that `master` has other significations than the master/slave meaning, and I personally never made this association in the past. However I'm also able to recognize that I...
2020 Jun 19
21
Inclusive language in LLVM: can we rename `master` branch?
...convention to name our development branch. On
SVN it used to be just "trunk".
This naming is unfortunate
<https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
it can hurt some contributors
<https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>, and
there is really no technical advantage that I know of to favor this
convention over another.
I am perfectly aware that `master` has other significations than the
master/slave meaning, and I personally never made this association in the
past. However I'm also able to recognize that I...
2020 Jun 19
2
Inclusive language in LLVM: can we rename `master` branch?
...pment branch. On
> SVN it used to be just "trunk".
>
> This naming is unfortunate
> <https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
> it can hurt some contributors
> <https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>,
> and there is really no technical advantage that I know of to favor this
> convention over another.
>
>
>
> I am perfectly aware that `master` has other significations than the
> master/slave meaning, and I personally never made this association in the
> past. However...
2020 Jun 19
2
Inclusive language in LLVM: can we rename `master` branch?
...pment branch. On
> SVN it used to be just "trunk".
>
> This naming is unfortunate
> <https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
> it can hurt some contributors
> <https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>,
> and there is really no technical advantage that I know of to favor this
> convention over another.
>
>
>
> I am perfectly aware that `master` has other significations than the
> master/slave meaning, and I personally never made this association in the
> past. However...
2020 Jun 19
3
Inclusive language in LLVM: can we rename `master` branch?
...pment branch. On
> SVN it used to be just "trunk".
>
> This naming is unfortunate
> <https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
> it can hurt some contributors
> <https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>,
> and there is really no technical advantage that I know of to favor this
> convention over another.
>
>
>
> I am perfectly aware that `master` has other significations than the
> master/slave meaning, and I personally never made this association in the
> past. However...
2020 Jun 19
6
Inclusive language in LLVM: can we rename `master` branch?
...t; convention to name our development branch. On SVN it used to be just "trunk".
This naming is unfortunate<https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as it can hurt some contributors<https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>, and there is really no technical advantage that I know of to favor this convention over another.
I am perfectly aware that `master` has other significations than the master/slave meaning, and I personally never made this association in the past. However I'm also able to recognize that I...
2020 Jun 19
3
Inclusive language in LLVM: can we rename `master` branch?
...pment branch. On
> SVN it used to be just "trunk".
>
> This naming is unfortunate
> <https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
> it can hurt some contributors
> <https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>,
> and there is really no technical advantage that I know of to favor this
> convention over another.
>
>
>
> I am perfectly aware that `master` has other significations than the
> master/slave meaning, and I personally never made this association in the
> past. However...
2020 Jun 19
5
Inclusive language in LLVM: can we rename `master` branch?
...pment branch. On
> SVN it used to be just "trunk".
>
> This naming is unfortunate
> <https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
> it can hurt some contributors
> <https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>,
> and there is really no technical advantage that I know of to favor this
> convention over another.
>
>
>
> I am perfectly aware that `master` has other significations than the
> master/slave meaning, and I personally never made this association in the
> past. However...
2020 Jun 19
4
Inclusive language in LLVM: can we rename `master` branch?
...pment branch. On
> SVN it used to be just "trunk".
>
> This naming is unfortunate
> <https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1> as
> it can hurt some contributors
> <https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf>,
> and there is really no technical advantage that I know of to favor this
> convention over another.
>
>
>
> I am perfectly aware that `master` has other significations than the
> master/slave meaning, and I personally never made this association in the
> past. However...
2020 Jun 21
8
Inclusive language in LLVM: can we rename `job` in source code?
<div> </div><div>Yes, broad. But what guys say: "You LLVM developers are all racists, because you use 'master' word"</div><div>Or broader: "You all developers are all racists, because you use 'master' word". We are not racists, but other guys think so.</div><div>So let's begin consistent and take into account all