From: Matt McCutchen <matt@mattmccutchen.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: Renaming the "master" branch without breaking existing clones
Date: Mon, 03 Aug 2020 20:43:34 -0400 [thread overview]
Message-ID: <0f1c557657b46ec4124ca37816a3e0aa4bd83501.camel@mattmccutchen.net> (raw)
In-Reply-To: <20200803160051.GA50799@syl.lan>
On Mon, 2020-08-03 at 12:00 -0400, Taylor Blau wrote:
> On Mon, Aug 03, 2020 at 08:15:58AM -0400, Matt McCutchen wrote:
> > 3. Ensuring that tools detect the default branch of a given repository
> > in an appropriate way rather than assuming "master". [...]
>
> I'm less qualified to talk about what's going on here, but my
> understanding is that providers and tool-makers are quite aware of this.
I'm not so sure about that. Recently I've been the most active
contributor to Braid (https://github.com/cristibalan/braid/), and I
only learned about this today when I stumbled on news about a similar
change to the Linux kernel and immediately wondered if git was doing
the same thing. I filed an issue (t
https://github.com/cristibalan/braid/issues/87) and will develop a fix
when I have time.
Matt
next prev parent reply other threads:[~2020-08-04 0:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 12:15 Renaming the "master" branch without breaking existing clones Matt McCutchen
2020-08-03 16:00 ` Taylor Blau
2020-08-03 16:19 ` Junio C Hamano
2020-08-03 16:39 ` Taylor Blau
2020-08-03 19:40 ` Jeff King
2020-08-03 20:40 ` Junio C Hamano
2020-08-03 20:45 ` Jeff King
2020-08-03 21:02 ` Junio C Hamano
2020-08-03 21:11 ` Jeff King
2020-08-03 21:38 ` Junio C Hamano
2020-08-04 0:37 ` Matt McCutchen
2020-08-04 0:43 ` Matt McCutchen [this message]
2020-08-03 16:14 ` Junio C Hamano
2020-08-03 17:41 ` Matt McCutchen
2020-08-03 18:20 ` Kaartic Sivaraam
2020-08-03 18:47 ` Junio C Hamano
2020-08-04 8:50 ` Kaartic Sivaraam
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=0f1c557657b46ec4124ca37816a3e0aa4bd83501.camel@mattmccutchen.net \
--to=matt@mattmccutchen.net \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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).