From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2020, #06; Mon, 29)
Date: Tue, 30 Jun 2020 08:06:27 +0700 [thread overview]
Message-ID: <20200630010627.GE20303@danh.dev> (raw)
In-Reply-To: <xmqqa70lfjvo.fsf@gitster.c.googlers.com>
On 2020-06-29 18:00:11-0700, Junio C Hamano <gitster@pobox.com> wrote:
> * js/default-branch-name (2020-06-24) 9 commits
> (merged to 'next' on 2020-06-25 at 8f962f9219)
> + testsvn: respect `init.defaultBranch`
> + remote: use the configured default branch name when appropriate
> + clone: use configured default branch name when appropriate
> + init: allow setting the default for the initial branch name via the config
> + init: allow specifying the initial branch name for the new repository
> + docs: add missing diamond brackets
> + submodule: fall back to remote's HEAD for missing remote.<name>.branch
> + send-pack/transport-helper: avoid mentioning a particular branch
> + fmt-merge-msg: stop treating `master` specially
> (this branch is used by hn/reftable.)
>
> The name of the primary branch in existing repositories, and the
> default name used for the first branch in newly created
> repositories, is made configurable, so that we can eventually wean
> ourselves off of the hardcoded 'master'.
>
> Will merge to 'master'.
Hi Junio,
I've posted a following up patch to change git-subtree in contrib
because of the change in fmt-merge-msg at <20200629162003.GD20303@danh.dev>
Don't know if it should be reviewed and merged separately, or it
should go with this topic?
--
Danh
next prev parent reply other threads:[~2020-06-30 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 1:00 What's cooking in git.git (Jun 2020, #06; Mon, 29) Junio C Hamano
2020-06-30 1:06 ` Đoàn Trần Công Danh [this message]
2020-06-30 15:39 ` Junio C Hamano
2020-06-30 19:14 ` Matheus Tavares Bernardino
2020-07-01 20:58 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200630010627.GE20303@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).