<div dir="ltr">While I appreciate this sentiment we should not block our changes on a project over which we have no control. Changing the name and the documentation is easy and we should do this today.<div><br></div><div>Thanks.</div><div><br></div><div>-eric</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 19, 2020 at 10:49 AM Petr Penzin via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <p>+1</p>
    <p>Git uses `master` branch in quite a few places in its docs and
      `git init` produces a
      `master` branch. ideally, a change to git should drive all of this
      - that way there would be no confusion.<br>
    </p>
    -Petr<br>
    <div><br>
    </div>
    <div>On 6/19/20 10:45 AM, Keane, Erich via
      llvm-dev wrote:<br>
    </div>
    <blockquote type="cite">
      
      
      
      <div>
        <p class="MsoNormal">I agree with this.  As much as I dislike
          the name that I believe github will choose, we should just do
          whatever everyone else is doing.<u></u><u></u></p>
        <p class="MsoNormal"><u></u> <u></u></p>
        <p class="MsoNormal">Note that in addition to the github
          discussion, there is some extensive discussion on the .git
          mailing list (IIRC) about choosing a new name as well.  I hope
          github waits until that choses a name as well.<u></u><u></u></p>
        <p class="MsoNormal"><u></u> <u></u></p>
        <div>
          <div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
            <p class="MsoNormal"><b>From:</b> llvm-dev
              <a href="mailto:llvm-dev-bounces@lists.llvm.org" target="_blank"><llvm-dev-bounces@lists.llvm.org></a> <b>On Behalf Of
              </b>Philip Reames via llvm-dev<br>
              <b>Sent:</b> Friday, June 19, 2020 10:39 AM<br>
              <b>To:</b> Mehdi AMINI <a href="mailto:joker.eph@gmail.com" target="_blank"><joker.eph@gmail.com></a>;
              llvm-dev <a href="mailto:llvm-dev@lists.llvm.org" target="_blank"><llvm-dev@lists.llvm.org></a><br>
              <b>Subject:</b> Re: [llvm-dev] Inclusive language in LLVM:
              can we rename `master` branch?<u></u><u></u></p>
          </div>
        </div>
        <p class="MsoNormal"><u></u> <u></u></p>
        <p>+1 to the notion of changing the branch name in general.<u></u><u></u></p>
        <p>However, I think there's a practical aspect which needs
          considered.  Currently, "master" is the defacto convention
          used across many, many projects.  There's currently a lot of
          conversation going on across many projects about naming.  I
          think it's really important that rather than just picking
          something that we wait and see what the new convention is, and
          adopt that.  I've seen reporting that GitHub is considering
          changing the default name for new projects.  If that does end
          up happening - I hope it does - I think we should use whatever
          name they pick.  Convention is critical for ease of use of new
          contributors.<u></u><u></u></p>
        <p>Philip<u></u><u></u></p>
        <p>p.s. There's a bunch of other terminology in use which is
          potentially problematic, but I'm intentionally restricting my
          response to this one.  I think each deserves discussion on
          it's own merits. 
          <u></u><u></u></p>
        <div>
          <p class="MsoNormal">On 6/19/20 2:48 AM, Mehdi AMINI via
            llvm-dev wrote:<u></u><u></u></p>
        </div>
        <blockquote style="margin-top:5pt;margin-bottom:5pt">
          <div>
            <div>
              <div>
                <p class="MsoNormal">Hi,<u></u><u></u></p>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">When we moved to GitHub a few
                    months ago, we used without more consideration the
                    "master" convention to name our development branch.
                    On SVN it used to be just "trunk".<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">This naming is <a href="https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1" target="_blank">
                      unfortunate</a> as it can <a href="https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf" target="_blank">
                      hurt some contributors</a>, and there is really no
                    technical advantage that I know of to favor this
                    convention over another.<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">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'm privileged here, and that not
                    everyone is in the same position.<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">As we intend to be an inclusive
                    community, I propose that we change the name of our
                    development branch and that we adopt instead a more
                    neutral terminology for the LLVM monorepo. Possible
                    names are "dev", "trunk", "main", "default", ...<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">We need to plan a transition as
                    all the bots will need to be updated to track this
                    new branch instead, but these are minor technical
                    details, nothing compared to the SVN->Git
                    migration we went through.<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">Since I'm on this topic, we
                    should also likely look into the pervasive use of
                    whitelist/blacklist in the project.<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">Thoughts?<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">-- <u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal">Mehdi<u></u><u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
                <div>
                  <p class="MsoNormal"><u></u> <u></u></p>
                </div>
              </div>
            </div>
          </div>
          <p class="MsoNormal"><br>
            <br>
            <u></u><u></u></p>
          <pre>_______________________________________________<u></u><u></u></pre>
          <pre>LLVM Developers mailing list<u></u><u></u></pre>
          <pre><a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><u></u><u></u></pre>
          <pre><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><u></u><u></u></pre>
        </blockquote>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
LLVM Developers mailing list
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
    </blockquote>
  </div>

_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>