From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id BDFC51F66F for ; Fri, 20 Nov 2020 00:37:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727054AbgKTAfH (ORCPT ); Thu, 19 Nov 2020 19:35:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726776AbgKTAfG (ORCPT ); Thu, 19 Nov 2020 19:35:06 -0500 Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 631E3C0613CF for ; Thu, 19 Nov 2020 16:35:06 -0800 (PST) Received: by mail-wm1-x330.google.com with SMTP id c198so6957826wmd.0 for ; Thu, 19 Nov 2020 16:35:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ENDQnME8JUp5WSnTTzcQDl4NQlZTLBHL960I1KsPuPQ=; b=WoSTXuxzCT0y5weuXqPv7X3J/PfGegKjaB6Q1BLiX01U1azNjVTV2BHw8XnX4TZp0X N8UC1z9yoR7iwJ7IiKnJZ8aT0DjrK1MVli1owcQE36EgRNEbzZEJKhn/2PM+jjdqH4vT T18oPQJuMWcElUZv/W0DrzS2WN0O5AGpwZjOA7SCmsUB+j38LxrwSlCHT7BbpTXcN2gU 4Oe2rNy25D6lyn804w1fN473X1O0Py2mIUcLdx5mOBLf6Dc9Tg8xoN+ZFew134DSNQg3 ET3SEaun0FtmecZ5qM5yodjja7Vb8v2eh972UOCL3Yt5RAJAi0MLtIRTprv6QjMwrbxE TxwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ENDQnME8JUp5WSnTTzcQDl4NQlZTLBHL960I1KsPuPQ=; b=sRVSAqJGX4+vaO59JuGO1tc3Lx0hOtC0XpNGgWYFzkiMIdVvx2kDr/m9oWoi644qyG H7IpIw/KDgysIM/IHV6B2pZEyvIXSxZE2Xtc6m17zYYB8aoPd1pZwW8qhOHw1tTgqQDI TJst4K4ttSKTOgkPHG0ItAYpskxmMM9ttiTcM79nw5StcKxyVocVHz7g9NQMVI3yzvkI MWVDTSDevM3EIoga5E0oLxGM/4RzHDFmZKPtz4sl/olQRuqaqbjXcKa9lZxwfA0rxWhC Wi692rXMVObdQKueH3QrmXAbi3co9AtCkqbgotQMTMUL2ky+rLO8jzmukihe3WdXk+qF szlg== X-Gm-Message-State: AOAM530Jnhj7iqjmCU0g03WddTr0zvB/zMkbLheK3nD/03H9K5PXpg2s 52MPM7eYdF0CzaBwGeiwByBsoERWIQAIXHPiJAk= X-Google-Smtp-Source: ABdhPJwroM6zQXqRlrvCCiWQMR7ME5wtvdMA9V+1fG7CZIw5i0IYuI9ABZCElx9mT2nc3wwWxvFl57kqjL/DoBIB4W0= X-Received: by 2002:a7b:cc94:: with SMTP id p20mr7409798wma.100.1605832505128; Thu, 19 Nov 2020 16:35:05 -0800 (PST) MIME-Version: 1.0 References: <20201113010107.GL6252@camp.crustytoothpaste.net> <20201113051408.GA3985404@mit.edu> <20201113145802.GB3985404@mit.edu> <20201115034649.GC3985404@mit.edu> <20201119133705.7q7yghymvvo7zeq4@chatter.i7.local> In-Reply-To: From: Felipe Contreras Date: Thu, 19 Nov 2020 18:34:54 -0600 Message-ID: Subject: Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco To: Brandon Casey Cc: "Theodore Y. Ts'o" , Lukasz Niemier , "brian m. carlson" , Git , Junio C Hamano , Johannes Schindelin , Don Goodman-Wilson Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Thu, Nov 19, 2020 at 3:29 PM Brandon Casey wrote: > On Thu, Nov 19, 2020 at 5:37 AM Konstantin Ryabitsev > wrote: > > To my knowledge, there are no concrete plans to change anything at this > > time. All recent work was to remove any special-case treatment of > > "master" as the default branch name, so people are free to use any > > configuration they like. > > Glad to hear that. That doesn't seem to be the perspective that others > have in this discussion thread though, especially since Theodore Ts'o > referred to "...the "master" -> "main" migration" in his comment that > I quoted above. Let me try to clarify to you. At this precise moment the name of the branch is "master", and will continue to be until a concrete plan to change it is put forward. However, the momentum is there to change the default name. So, if the camp in favor of the change keeps pushing forward, finishes all the necessary work, and puts a plan in place--which will probably include a precautionary warning--the name will likely be eventually changed. It's only a matter of when. Since there's many agendas: a) get the name changed as soon as possible, b) change the name, but do it properly and take as long as is indeed, c) change the name, but not necessarily to "main", and d) do not change the name; what you are seeing is probably a clash of many agendas and no clarity from the project. Moreover, once the plan is set in motion, and many users are notified of things upcoming change, I suspect there will be a backlash, and the "decision" might be reconsidered. So, even though things are not set in stone, and the dust has not yet settled, the move towards a change away from the default branch name "master" is currently happening. Cheers. -- Felipe Contreras