From: Jeff King <peff@peff.net>
To: Elijah Newren <newren@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>,
Git Mailing List <git@vger.kernel.org>,
James Ramsay <jramsay.com.au@syl.local>,
Bryan Turner <bturner@atlassian.com>
Subject: Re: Consensus on a new default branch name
Date: Tue, 16 Jun 2020 10:32:02 -0400 [thread overview]
Message-ID: <20200616143202.GM666057@coredump.intra.peff.net> (raw)
In-Reply-To: <CABPp-BE3UAeMKCtwnTf-5ifVhveRPzQfT1T+sHsm_LDOubCHCQ@mail.gmail.com>
On Mon, Jun 15, 2020 at 03:38:08PM -0700, Elijah Newren wrote:
> As I stated in the other thread[1], I'm happy 'default' isn't winning
> because I think it can lead to ambiguity about the meaning of the
> phrase "default branch" (particularly when someone changes HEAD on the
> server to point to anything other than "refs/heads/default"). I don't
> think "main branch" poses similar issues, as it's not a phrase I've
> seen used that much (in contrast to "default branch"). Also,
> "default" being ambiguous bothers me personally more than other terms
> being ambiguous, as per my story in the other thread. However, it's
> possible that there is documentation or guides somewhere that have
> used "main branch" in the past and could become ambiguous with the
> proposed change, and thus would benefit from updates.
Thanks for writing this out (I'm still catching up on list email after a
vacation, so I missed the earlier thread). It really cemented for me
that "main" is better than "default".
-Peff
next prev parent reply other threads:[~2020-06-16 14:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:57 Consensus on a new default branch name Taylor Blau
2020-06-15 21:10 ` Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31 ` Jeff King
2020-06-16 14:52 ` Oleg
2020-06-16 16:00 ` Jeff King
2020-06-16 17:11 ` Oleg
2020-06-16 17:32 ` Konstantin Ryabitsev
2020-06-16 18:54 ` Oleg
2020-06-16 22:18 ` Jeff King
2020-06-16 16:10 ` Konstantin Ryabitsev
2020-06-16 16:13 ` Santiago Torres Arias
2020-06-16 16:48 ` Jeff King
2020-06-16 16:14 ` Jason Pyeron
2020-06-16 16:47 ` Jeff King
2020-06-16 17:44 ` Steve Litt
2020-06-16 19:00 ` Oleg
2020-06-17 18:06 ` Michal Suchánek
2020-07-01 17:31 ` Michal Suchánek
2020-07-01 21:57 ` Jeff King
2020-07-02 12:21 ` Whinis
2020-07-02 21:15 ` Philip Oakley
2020-07-02 21:59 ` Whinis
2020-07-02 22:47 ` Philip Oakley
2020-07-02 23:08 ` Whinis
2020-07-01 22:25 ` Jonathan Nieder
2020-06-15 22:38 ` Elijah Newren
2020-06-16 14:32 ` Jeff King [this message]
2020-06-17 20:13 ` Junio C Hamano
2020-06-15 23:24 ` brian m. carlson
2020-06-16 0:50 ` James Ramsay
2020-06-16 1:58 Nomen Nescio
2020-06-16 2:22 ` Jonathan Nieder
2020-06-16 2:31 ` Taylor Blau
2020-06-16 14:38 ` Jeff King
2020-06-17 0:01 Anonymous Remailer (austria)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200616143202.GM666057@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=jramsay.com.au@syl.local \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.