From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: js/init-defaultbranch-advice, was Re: What's cooking in git.git (Dec 2020, #01; Tue, 8)
Date: Wed, 09 Dec 2020 13:57:56 -0800 [thread overview]
Message-ID: <xmqqft4e1w2j.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2012091510280.25979@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 9 Dec 2020 15:11:44 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> On Tue, 8 Dec 2020, Junio C Hamano wrote:
>
>> * js/init-defaultbranch-advice (2020-11-24) 4 commits
>> - init: provide useful advice about init.defaultBranch
>> - get_default_branch_name(): prepare for showing some advice
>> - branch -m: allow renaming a yet-unborn branch
>> - init: document `init.defaultBranch` better
>>
>> Our users are going to be trained to prepare for future change of
>> init.defaultBranch configuration variable.
>>
>> Expecting a reroll.
>> cf. <xmqq8saqjx2n.fsf@gitster.c.googlers.com>
>> I think a new advice.defaultBranchName is a bad idea.
>
> Unfortunately, this objection is news to me. Why would it be anything but
> a legitimate interest to say "yeah, whatever, Git, just use the default
> branch name, I'm fine with it"?
Message sent on Nov 24 is a news to you now?
Anyway, I do not think those users who said "I'm fine with it" would
be fine when the switchover happens outside their control.
If they are truly fine, we could invent init.defaultBranch=:random
that chooses a random branch name and point HEAD at it, and make
that the default. Those who are fine do not really care what name
the initial branch gets would be fine with that as well, but you
would agree that it is an absurd alternative, no? I find it equally
absurd to say "switch to a new name any time without telling me, I
am fine with it".
next prev parent reply other threads:[~2020-12-09 21:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 1:31 What's cooking in git.git (Dec 2020, #01; Tue, 8) Junio C Hamano
2020-12-09 1:41 ` Taylor Blau
2020-12-10 2:02 ` Jonathan Tan
2020-12-09 2:45 ` Elijah Newren
2020-12-09 4:22 ` Junio C Hamano
2020-12-09 23:02 ` Taylor Blau
2020-12-10 0:57 ` Junio C Hamano
2020-12-10 2:57 ` Jonathan Tan
2020-12-09 14:09 ` fc/pull-merge-rebase, was " Johannes Schindelin
2020-12-09 21:28 ` Junio C Hamano
2020-12-10 0:31 ` Felipe Contreras
2020-12-10 4:40 ` Johannes Schindelin
2020-12-10 4:46 ` Johannes Schindelin
2020-12-10 15:11 ` Felipe Contreras
2020-12-10 15:27 ` Theodore Y. Ts'o
2020-12-10 18:28 ` Junio C Hamano
2020-12-11 1:33 ` Felipe Contreras
2020-12-11 7:17 ` Junio C Hamano
2020-12-11 14:10 ` Felipe Contreras
2020-12-11 22:09 ` Theodore Y. Ts'o
2020-12-12 0:43 ` Felipe Contreras
2020-12-10 0:27 ` Felipe Contreras
2020-12-11 5:59 ` Junio C Hamano
2020-12-09 14:11 ` js/init-defaultbranch-advice, " Johannes Schindelin
2020-12-09 21:57 ` Junio C Hamano [this message]
2020-12-10 4:54 ` Johannes Schindelin
2020-12-10 18:33 ` Junio C Hamano
2020-12-11 0:03 ` Felipe Contreras
2020-12-10 3:56 ` bc/rev-parse-path-format, " Johannes Schindelin
2020-12-10 18:34 ` 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=xmqqft4e1w2j.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).