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 9629A1F670 for ; Thu, 19 Nov 2020 21:32:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726300AbgKSV3r (ORCPT ); Thu, 19 Nov 2020 16:29:47 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44218 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726154AbgKSV3r (ORCPT ); Thu, 19 Nov 2020 16:29:47 -0500 Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E7B8FC0613CF for ; Thu, 19 Nov 2020 13:29:46 -0800 (PST) Received: by mail-il1-x12c.google.com with SMTP id q1so6716996ilt.6 for ; Thu, 19 Nov 2020 13:29:46 -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; bh=eHiXaR1J+vzUhx4T9RfE2Qto+JUIlVKVl3iaiVkpKOg=; b=G8XmoKq7Mda+Hcqu8ZxVELWZAd86oLfl/mGIceDm5EqddiOVNK90wOBCz+4uJ2f1CG CO0qzxmczy8ov8kjDsYI5gbXStS9Po+B/bS+VgO0630uX2yQRCTi8XsSh+P7cdokC4I3 Vrp6J03K45nBH4MYkGN5QkgHx2LUao8bbb827DZPKdBNFbiGwT4gBY/uQUxgq7WKopLM 1QTH7MbErIJIVMD7KpKFRofLyCGF9BYOTAXYkGv+0gF1KAQrP14xXzC2OblY9Opf04bI 7EMcXz9DIOW+ccP5lcapjrx6dR5rRF/6EH1v2Vxj4EPtzv/HJ0YbPOg1fmHpbeimTxUq vnZg== 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; bh=eHiXaR1J+vzUhx4T9RfE2Qto+JUIlVKVl3iaiVkpKOg=; b=SU0Tlucp2BWYHKQ6+hxzSYjSj2TgoVvZ2MN/ivQeTBUUOLJfbN1G0giZOZvqYvEblm r4Jt23pzuNuzi+7A1lP++M6sW/8y53Xffs+hDW0TNWbzIRuLeNvtmEHSHhEI03M2Vw1v RxEfVYdTeZ8yDRJv1FnOBxjIDBrR8KW1ioPH9BAgBPY5UYbJJZDj6oODP3+Uu3/DZBEl JJs/8sxYdyZ6iruDWg6uD3evbpcU0hazcFjCUM49MNi8PcNUBqcnXpyunr+AqByqG82y NOjQyc5arcp0zLQUsjV0HgNCkMTI0n95I6vS7V5otT4VpwvlnPifac/7/sJcXgsuShVe x/uA== X-Gm-Message-State: AOAM533a0paquZOfwVMz6PV1TsEWoLzidhES1WWD8lL2fOb6w21Yaabu NFHAaPNvad801afaC0oMIcTN2KZWsK4ADY9dtg0= X-Google-Smtp-Source: ABdhPJxD8xk7pI3VS1uM+0Ow66+BKI8yzEMcujCO0103N5SCtX5my7eJZ2LOSK4t3wq/UTxwf+e6GvGU56hZCfKGzLo= X-Received: by 2002:a92:de50:: with SMTP id e16mr22909978ilr.144.1605821386275; Thu, 19 Nov 2020 13:29:46 -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: <20201119133705.7q7yghymvvo7zeq4@chatter.i7.local> From: Brandon Casey Date: Thu, 19 Nov 2020 13:29:35 -0800 Message-ID: Subject: Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco To: Brandon Casey , "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 On Thu, Nov 19, 2020 at 5:37 AM Konstantin Ryabitsev wrote: > > On Wed, Nov 18, 2020 at 05:02:59PM -0800, Brandon Casey wrote: > > > This *really* is not hard; which is why I am starting to suspect > > > people are really kvetching because their objections are really more > > > about the woke/anti-woke aspect of the "master" -> "main" migration > > > --- and they are using *think* the children^H^H^H^H^H^H^H users as a > > > rhetorical device. > > > > So we're changing the default branch name from "master" to "main"? > > 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. Thanks for trying to respond to my questions, but I think your responses are mostly misdirected towards an issue that I was not referring to. That being the configurability of the default branch name, which I doubt anyone has a problem with, as opposed to changing the default branch name for all newly created repositories and possibly for the git repo itself for some supposed offensiveness of the word "master". That is what I consider silly. For example, when I asked "So we're changing the default branch name from "master" to "main"?" and then followed that up with "For what purpose?", the latter question was asking "For what purpose are we changing the default branch name from "master" to "main"?", and then "What problem are we trying to solve by changing the default branch name from "master" to "main"?" etc. -Brandon