From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Han-Wen Nienhuys <hanwen@google.com>
Cc: git <git@vger.kernel.org>
Subject: RE: [PATCH] SQUASH??? allow t0031 to run with any default branch name
Date: Mon, 21 Dec 2020 14:19:57 -0600 [thread overview]
Message-ID: <5fe1036d63729_f938208b3@natae.notmuch> (raw)
In-Reply-To: <xmqqsg7zkk75.fsf_-_@gitster.c.googlers.com>
Junio C Hamano wrote:
> It seems that we should stop assuming what the name of the default
> branch is in a new repository. One good way to do so would be to
> change "git init" to "git init -b primary" so that the tests won't
> get affected whether the default name is master or main or any other
> value, and then use 'primary' throughout the name, instead of
> assuming 'master' will stay to be the name used when unspecified
> forever.
A better name would be "initial".
Even in tests branch names should mean something, and in the context of
git, the master branch means the original branch from which all the
other branches were copied from (usually). In tests the primary branch
is not necessarily the master branch, so "primary" doesn't cut it.
Another option is "original".
If the meaning of the word is not defined yet, a placeholder can be "nonce".
Or if we don't want to assign any meaning at all, just "blank", "nil",
and of course "foobar".
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2020-12-21 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 5:34 What's cooking in git.git (Dec 2020, #03; Fri, 18) Junio C Hamano
2020-12-19 6:44 ` Eric Sunshine
2020-12-19 17:13 ` Junio C Hamano
2020-12-19 14:10 ` Felipe Contreras
2020-12-19 17:09 ` Junio C Hamano
2020-12-20 2:19 ` Elijah Newren
2020-12-20 7:32 ` Junio C Hamano
2020-12-21 17:25 ` Elijah Newren
2020-12-21 17:50 ` Junio C Hamano
2020-12-21 12:40 ` Han-Wen Nienhuys
2020-12-21 18:01 ` Junio C Hamano
2020-12-21 19:55 ` [PATCH] SQUASH??? allow t0031 to run with any default branch name Junio C Hamano
2020-12-21 20:19 ` Felipe Contreras [this message]
2020-12-22 10:22 ` Han-Wen Nienhuys
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 18:01 Junio C Hamano
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=5fe1036d63729_f938208b3@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanwen@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).