From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Daniel Gruesso <daniel.gruesso@gmail.com>,
"Patricia B. C." <pati.camsky@gmail.com>,
Martin von Zweigbergk <martinvonz@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: RES: Can git change?
Date: Wed, 10 Mar 2021 13:39:59 -0800 [thread overview]
Message-ID: <xmqqy2euit74.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2103101038170.50@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 10 Mar 2021 22:03:29 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> I guess that something like 6 months of a "deprecation period" (i.e. the
> time to keep `master` as the default) _might_ be enough, so we could
> potentially move forward with changing the default around end of May (by
> my calculation, v2.32.0 should be due around May 24th, that might be a
> good candidate to target).
You are apparently more ambitious and risk tolerant than I am. I
was expecting it to be more towards the end of the year myself.
And we already made sure that it would be easy to interact with
projects by using the same primary branch name as the upstream
project uses when cloning; hopefully by the time we change the
built-in hardcoded fallback default, it would not have much impact
to the real life usability than it is a symbolic act.
prev parent reply other threads:[~2021-03-10 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 12:59 Can git change? Patricia B. C.
2021-01-22 13:31 ` Christian Couder
2021-01-22 18:46 ` Junio C Hamano
2021-01-22 22:43 ` Martin von Zweigbergk
2021-01-23 2:27 ` Junio C Hamano
2021-01-23 12:56 ` RES: " Patricia B. C.
2021-01-25 16:28 ` Johannes Schindelin
2021-01-26 1:58 ` Junio C Hamano
2021-01-26 12:32 ` Patricia B. C.
2021-03-09 14:54 ` Daniel Gruesso
[not found] ` <CAFdpPnBG==5L6hwH6h2JTFtYVQqLZUcCi4+wzL_cpKKg_X3yoA@mail.gmail.com>
2021-03-10 21:03 ` Johannes Schindelin
2021-03-10 21:39 ` Junio C Hamano [this message]
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=xmqqy2euit74.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=daniel.gruesso@gmail.com \
--cc=git@vger.kernel.org \
--cc=martinvonz@gmail.com \
--cc=pati.camsky@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 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).