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.6 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 81D4F1F66F for ; Thu, 19 Nov 2020 04:20:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726188AbgKSEQw (ORCPT ); Wed, 18 Nov 2020 23:16:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54252 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726105AbgKSEQw (ORCPT ); Wed, 18 Nov 2020 23:16:52 -0500 Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E4F50C0613D4 for ; Wed, 18 Nov 2020 20:16:51 -0800 (PST) Received: by mail-pf1-x436.google.com with SMTP id t8so3193555pfg.8 for ; Wed, 18 Nov 2020 20:16:51 -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=fxFEJO35R7eA2gdjtYOLprXdB33nEK1DufpgP4QV0pY=; b=o00XZ4zgno2FJl4RFmduQ5ad0PXY2Aj6/zt2DAKBXeDOsJeatTZ08YafF5gSzqZLfU DrlFjfpeixyVfGCfL/zCcelAgDPZsXyiBDSmdQzMvThrpmCeUEvrk1CX9Dg0vsg/tQyf 07MRnJsGUrArtXE/FKWb8Je6gKD9mMSHSilJAUfuAxS4oGaRFpTrWvFt6cbJ9SLna1JS ovgrAa+9e7jBMSEmQ0EBNMYjhhS9P3IZ3/A3KUQnxZVZ94GofYkqnCAoTEEKNyyS1RAd HikD2W6j8Y5YTwEvuWvkZCb6mDYUCyeEC3lUXDBAGKi0UNccnEYTC5F7C1/LlQZVwkjk erLw== 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=fxFEJO35R7eA2gdjtYOLprXdB33nEK1DufpgP4QV0pY=; b=HpXCCyHKfBR6B6vCeUnX5ocgiBBY4tAQSEe4j5QQ3ZSOLt1MJP9qMpAvtRQUwgMx3G O5oNfVU9dzb3np9Ho3NsnLdy1+PAjdQVYmf3ZvP9tVEgREK8IOJqvA3Qv0sFJsZrMJkz EFijWE3W3qE0pB4ueoD4CrSwrrlzLV3C4/zOBCn52LJplD62uCBM3sN6c/mUKFELRdjJ rswjBufc1DvI2Iq/aHDLC1U+PYZT2bHvBNFetoH/uZHi8x+BAobGzuVO8gq85/jcgReH TTudTRlFL+4fc+6pkbxekIzt5n9kNu/Q5lw1Am9t1T1dSFzbSYdF5GQTmOiGDHtfTGkt 1c2w== X-Gm-Message-State: AOAM530iXXM1xupj/3fTV86wTbZb5ds3kMpYqrsHQGhrkG9F6NxzhPMy YRjmfSODQBXNOGFHxI/n5wZl7daKe2kWrimCHAE= X-Google-Smtp-Source: ABdhPJyaSfHSgMQBY27oowGcaQp1ClrQuFn1zXZZHbga06867teA9yae/zToI/YedXdY+UxSg1w8yTAZ9yERRjpLvls= X-Received: by 2002:a17:90a:2c09:: with SMTP id m9mr2175969pjd.205.1605759411329; Wed, 18 Nov 2020 20:16:51 -0800 (PST) MIME-Version: 1.0 References: <20201113010107.GL6252@camp.crustytoothpaste.net> <20201113051408.GA3985404@mit.edu> <20201113145802.GB3985404@mit.edu> <20201115034649.GC3985404@mit.edu> In-Reply-To: From: Peter Hadlaw Date: Wed, 18 Nov 2020 22:16:25 -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 , Felipe Contreras , "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 Reposting a bit from a side thread, so excuse me. Felt that this is more of a relevant place to leave these thoughts. *** If some people or teams would prefer _their_ default branches to be anything other than `master`, I'm all for giving them the tools to live out their dreams. That's what `git config` and the new `defaultBranch` flag are for. There is no need to force these desires onto _all_ users. *** It's worth noting that the word "slave" comes from the en_slav_ement of Slavs (the Slavic people of Eastern Europe). Check "Slav Twitter" if you must, you'll find nothing but a chuckle at this situation. I encourage everyone to really think about the changes you are making. It was just reported to me that a professional friend of mine had confusion as to why, after initializing a new repository, they couldn't navigate to the `master` branch of their repository. I understand this is back-of-the-napkin type math but stay with me for one moment. I also understand GitHub is not all of git users, but I just pulled the number to help me out here. If GitHub has 40 million users but let's say half of them aren't active, so now we are at 20 million. (Replace this number with how many actual users of git are out there.) Let's even say half of them are on board and aware of this "harmless" change to a more "sensitive" doublespeak representation of the "master" copy/branch of the repo. That leaves us with 10 million users of git that are either unaware or are not on board. Let's say it takes 3 minutes for a user to search on the web why exactly they can't navigate to their "master" branch. That's 30 million minutes wasted, or about 57 man-YEARs of time wasted.... for what? Oh but you'll ask them what their default is? Do the same math... better yet realize this is just a power exercise of one very tiny group over another. When do we put our foot down and say enough is enough, and not everything is offensive? Again, please reconsider making this change towards doublespeak/Newspeak and consider the ramifications of how much actual human life & time will be wasted. Ignoring adding on the new reputation of the git project to kowtow to "current year" politics. Besides just the annoyance to users in their day to day, yes there is mention of "just update the tutorials!" but what a way to dishonor the millions of hours people have put into welcoming other individuals to the git community. There is no reason to outdate their tutorials and documentation so prematurely (and yet again exercise power over them by making them update their content for no real reason). -- Peter