public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ben Knoble <ben.knoble@gmail.com>
Cc: Ryan Johnson <ryan.johnson.code@gmail.com>,  git@vger.kernel.org
Subject: Re: git branch behavior after git init needs fixing
Date: Mon, 09 Feb 2026 09:08:15 -0800	[thread overview]
Message-ID: <xmqqjywl6e0w.fsf@gitster.g> (raw)
In-Reply-To: <D1CA4E13-B279-4931-81EF-364169564612@gmail.com> (Ben Knoble's message of "Mon, 9 Feb 2026 09:54:25 -0500")

Ben Knoble <ben.knoble@gmail.com> writes:

> You are probably looking for init.defaultBranch and the 3.0
> breaking changes plan (which will make main the default).

In other words, run

    $ git config --global init.defaultbranch main

just once to live in the future?  That sounds like a sensible
suggestion to me.


  reply	other threads:[~2026-02-09 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  9:43 git branch behavior after git init needs fixing Ryan Johnson
2026-02-09 14:54 ` Ben Knoble
2026-02-09 17:08   ` Junio C Hamano [this message]
2026-02-09 22:38     ` 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=xmqqjywl6e0w.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ryan.johnson.code@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