All of lore.kernel.org
 help / color / mirror / Atom feed
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, #02; Mon, 14)
Date: Tue, 15 Dec 2020 12:59:39 -0800	[thread overview]
Message-ID: <xmqqczza945g.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2012151708110.25979@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 15 Dec 2020 17:09:10 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Mon, 14 Dec 2020, Junio C Hamano wrote:
>
>> * js/init-defaultbranch-advice (2020-12-13) 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.
>
> Do I understand correctly that you won't consider this for v2.30.0?

It is not even in 'next' yet, so it is too early to decide if we'd
keep it in 'next' until the final, or we'd like it so much that we'd
merge it to 'next' and then down to 'master' before -rc's.

So, no, you do not understand correctly.

I have the latest from you, I think, and I do not recall seeing
anything fishy in it myself, so I am leaning toward merging it at
least to 'next', but I do not know right at this moment how strongly
others support its inclusion in the upcoming release.

Thanks for pinging.

      reply	other threads:[~2020-12-15 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 20:04 What's cooking in git.git (Dec 2020, #02; Mon, 14) Junio C Hamano
2020-12-15 16:09 ` js/init-defaultbranch-advice, was " Johannes Schindelin
2020-12-15 20:59   ` 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=xmqqczza945g.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 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.