"Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > diff --git a/Documentation/config/core.txt b/Documentation/config/core.txt > index 74619a9c03b..a11e1abdf59 100644 > --- a/Documentation/config/core.txt > +++ b/Documentation/config/core.txt > @@ -626,3 +626,7 @@ core.abbrev:: > in your repository, which hopefully is enough for > abbreviated object names to stay unique for some time. > The minimum length is 4. > + > +core.defaultBranchName:: > + Allows overriding the default branch name e.g. when initializing > + a new repository or when cloning an empty repository. As we saw in [PATCH 7/9], it also affects for which branch an auto-generated merge message omits "into $branch" at the end. The behaviour change of "merge" might matter more than we think here in a hand-wavy way, and it certainly does affect more than 'init' and 'clone' (both of which are one time operation per repository), because setting this in ~/.gitconfig would affect all the repositories, whose merges into their 'master' suddenly starts saying "into master" at the end, unlike existing merges. So it probably is worth highlighting it here. > diff --git a/t/README b/t/README > index cf863837ab9..b32f520a27f 100644 > --- a/t/README > +++ b/t/README > @@ -421,6 +421,10 @@ GIT_TEST_DISALLOW_ABBREVIATED_OPTIONS=<boolean>, when true (which is > the default when running tests), errors out when an abbreviated option > is used. > > +GIT_TEST_DEFAULT_BRANCH_NAME allows overriding the default branch name > +that is used for example when initializing new repositories, or when > +cloning a repository that has no branches yet. > + > Naming Tests > ------------
