All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: Getting rid of "hint: Using 'master' as the name for the initial branch." when initializing a repository with pygit
Date: Tue, 1 Feb 2022 15:15:52 -0500	[thread overview]
Message-ID: <YfmU+D7wB2ePMGTZ@nand.local> (raw)
In-Reply-To: <20220201200246.GW3113@kunlun.suse.cz>

On Tue, Feb 01, 2022 at 09:02:46PM +0100, Michal Suchánek wrote:
> On Tue, Feb 01, 2022 at 02:52:41PM -0500, Taylor Blau wrote:
>
> > If you have set the init.defaultBranch configuration, we will suppress
> > the hint you're talking about.
>
> That's the problem - there is no way to pass the configuration when
> using a library to create a repository.

Of course; but I was suggesting that you set it in $HOME/.gitconfig, or
in your global /etc/gitconfig.

> > Alternatively, you can make sure that `git init` is invoked with the
> > `-q` (quiet) flag, which suppresses that warning whether or not you have
> > set the init.defaultBranch config.
>
> Yes, that is exactly the option that would do it.

OK, I assume that this means that you can pass custom flags down to `git
init` via the library you're using.

Thanks,
Taylor

  reply	other threads:[~2022-02-01 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 18:41 Getting rid of "hint: Using 'master' as the name for the initial branch." when initializing a repository with pygit Michal Suchánek
2022-02-01 19:52 ` Taylor Blau
2022-02-01 20:02   ` Michal Suchánek
2022-02-01 20:15     ` Taylor Blau [this message]
2022-02-01 19:59 ` Getting rid of "hint: Using 'master' as the name for the initial branch." when not " Michal Suchánek

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=YfmU+D7wB2ePMGTZ@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=msuchanek@suse.de \
    /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.