From: Santiago Torres Arias <santiago@nyu.edu>
To: Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org, James Ramsay <james@jramsay.com.au>,
Bryan Turner <bturner@atlassian.com>
Subject: Re: Consensus on a new default branch name
Date: Tue, 16 Jun 2020 12:13:31 -0400 [thread overview]
Message-ID: <20200616161331.7gosaynkqg5ofgwn@LykOS.localdomain> (raw)
In-Reply-To: <20200616161001.fa5wa2br5ois2csr@chatter.i7.local>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On Tue, Jun 16, 2020 at 12:10:01PM -0400, Konstantin Ryabitsev wrote:
> On Tue, Jun 16, 2020 at 10:31:07AM -0400, Jeff King wrote:
> >
> > My biggest concern here was trying to understand what could break.
> > Having read the patches from Johannes and thought about it a lot, I have
> > a pretty good handle on where Git itself cares about the name. And I
> > feel pretty confident that we can make the change in a way that won't
> > cause problems there (and in fact, I think some of the code will be
> > made more robust by relying on HEAD more appropriately).
> >
> > There's a more open question of what _else_ will break in the ecosystem.
>
> What if we work on making this configurable for now, but stick with the
> legacy name until we introduce breaking sha1 changes? Almost everything
> will need to retool for those anyway (and all documentation rewritten),
> so it is reasonable to bundle these changes to happen at the same time.
I wonder if allowing the buildsystem to set this default value would be
a wortwhile stepping stone. This way we can test things in different
ecosystems.
Thoughts?
-Santiago
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-16 16:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:57 Consensus on a new default branch name Taylor Blau
2020-06-15 21:10 ` Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31 ` Jeff King
2020-06-16 14:52 ` Oleg
2020-06-16 16:00 ` Jeff King
2020-06-16 17:11 ` Oleg
2020-06-16 17:32 ` Konstantin Ryabitsev
2020-06-16 18:54 ` Oleg
2020-06-16 22:18 ` Jeff King
2020-06-16 16:10 ` Konstantin Ryabitsev
2020-06-16 16:13 ` Santiago Torres Arias [this message]
2020-06-16 16:48 ` Jeff King
2020-06-16 16:14 ` Jason Pyeron
2020-06-16 16:47 ` Jeff King
2020-06-16 17:44 ` Steve Litt
2020-06-16 19:00 ` Oleg
2020-06-17 18:06 ` Michal Suchánek
2020-07-01 17:31 ` Michal Suchánek
2020-07-01 21:57 ` Jeff King
2020-07-02 12:21 ` Whinis
2020-07-02 21:15 ` Philip Oakley
2020-07-02 21:59 ` Whinis
2020-07-02 22:47 ` Philip Oakley
2020-07-02 23:08 ` Whinis
2020-07-01 22:25 ` Jonathan Nieder
2020-06-15 22:38 ` Elijah Newren
2020-06-16 14:32 ` Jeff King
2020-06-17 20:13 ` Junio C Hamano
2020-06-15 23:24 ` brian m. carlson
2020-06-16 0:50 ` James Ramsay
-- strict thread matches above, loose matches on Subject: below --
2020-06-16 1:58 Nomen Nescio
2020-06-16 2:22 ` Jonathan Nieder
2020-06-16 2:31 ` Taylor Blau
2020-06-16 14:38 ` Jeff King
2020-06-17 0:01 Anonymous Remailer (austria)
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=20200616161331.7gosaynkqg5ofgwn@LykOS.localdomain \
--to=santiago@nyu.edu \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=james@jramsay.com.au \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).