List for cgit developers and users
 help / color / mirror / Atom feed
From: "Jan Drögehoff" <sentrycraft123@gmail.com>
To: cgit@lists.zx2c4.com
Subject: Re: [PATCH] use main as default branch instead of master
Date: Sun, 9 Jan 2022 13:53:22 +0100	[thread overview]
Message-ID: <817460f2-2e3a-a385-76c4-685ce2c92700@gmail.com> (raw)
In-Reply-To: <20220109030454.r2gxxox4hzz5uf6g@feather>

> Replacing one hard coded value with another is really not helpful.
> Git itself solves this locally with init.defaultBranch in its config.
>
> If the corresponding option is unset you are helpfully told to choose
> one. That is however not simply a matter of s/master/main/ but the
> following:
>
>> Names commonly chosen instead of 'master' are 'main', 'trunk' and
>> 'development'.
> As you can see, multiple "common" options.

At the moment I think its better to simply stay with 'master' since that 
is what Git uses as the default at the moment

even if multiple git hosting sites have decided to adopt main

> There's work ongoing in git to make this more streamlined,
> last example I know being
>
>    commit e06c9e1df28e04bbf013840c6c50ce1be41b9583
>    Author: Thomas Weißschuh <thomas@t-8ch.de>
>    Date:   Wed Nov 3 21:17:02 2021 +0100
>
>    var: add GIT_DEFAULT_BRANCH variable.
>
> There's also similar efforts that would allow querying a remote.
>
> So I'd suggest you wait for upstream to figure it out first, rather than
> blindly substituting the term which would break existing setup for no
> real reason.

  reply	other threads:[~2022-01-09 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09  1:45 Derek Stevens
2022-01-09  3:04 ` Reto
2022-01-09 12:53   ` Jan Drögehoff [this message]
2022-01-09 17:22     ` Derek Stevens

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=817460f2-2e3a-a385-76c4-685ce2c92700@gmail.com \
    --to=sentrycraft123@gmail.com \
    --cc=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).