From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) by sourceware.org (Postfix) with ESMTP id 45FFE386F002 for ; Fri, 3 Jul 2020 15:20:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 45FFE386F002 Received: from mail-qk1-f198.google.com (mail-qk1-f198.google.com [209.85.222.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-427-M1Gw67fkOI-QJFzJ-TYeQw-1; Fri, 03 Jul 2020 11:20:13 -0400 X-MC-Unique: M1Gw67fkOI-QJFzJ-TYeQw-1 Received: by mail-qk1-f198.google.com with SMTP id 204so21854635qki.20 for ; Fri, 03 Jul 2020 08:20:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=VGyOQp7Km9m5TwuCCvusDY0N+vCt7H9cvKLOo9+49Ng=; b=paHbj7+nWC3Mfu5Ccx5MBTJIXs0TnrDVRTBkNjloMiVMLZ9TzFxkrMQ5mpKn3rdaV9 DKiD5NwYk3AUfTbNp2WwcgKRS9Jf1b9a3OSUEcgsjIDW4rK0KMEF3qIwTcLOBuq5d79s uIvikS3ABb8afd3XtxL125ACdwX/p8fWUMrkbIGTvvSQfzYOEMUYASbWpxjNZXCpW2Ce X57JCtu6HHksLKenjB4qSRfaXs5jVBkw6MTZr+JsRRYkYtLA2xwA1WPOMvkKQBGMyGw+ 8zP+XrfvLPpsUf96H2uV43fUpqUgBrIUTCNynkEQ1dP3osYoy+YSEFuYRVm8d07NY/xj OB1g== X-Gm-Message-State: AOAM531mGzVKbdPtv811b3dA87AAyf4AfR8QWsLMLkHFXnC8CUKsBjWy /ZBOEy5UBWef314ABDNAvPGjldrfkQRedP3QaNICrBE8qrJhkPZc7ek2U9nyDVrMM6AdCRSGtTk w4JmPH0cu5WOShzNt+9LF X-Received: by 2002:a05:6214:178c:: with SMTP id ct12mr3792989qvb.64.1593789612855; Fri, 03 Jul 2020 08:20:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy5FVpOkTx5EQaljeEd6BhfZ4J2RIlMFgNzkm+wLKIyaeGqw1fDN7Mcj//lBlPzg6rLiy5/+g== X-Received: by 2002:a05:6214:178c:: with SMTP id ct12mr3792973qvb.64.1593789612642; Fri, 03 Jul 2020 08:20:12 -0700 (PDT) Received: from [192.168.1.4] (198-84-170-103.cpe.teksavvy.com. [198.84.170.103]) by smtp.gmail.com with ESMTPSA id c9sm11287087qtn.87.2020.07.03.08.20.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Jul 2020 08:20:11 -0700 (PDT) Subject: Re: Rename "master" branch to "main"? To: Michael Kerrisk , Zack Weinberg Cc: libc-alpha , "Joseph S. Myers" , Florian Weimer , Paul Eggert References: From: Carlos O'Donell Organization: Red Hat Message-ID: <3986c3aa-78c2-dc78-e268-edf73d4adb4c@redhat.com> Date: Fri, 3 Jul 2020 11:20:10 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2020 15:20:17 -0000 On 7/2/20 4:58 PM, Michael Kerrisk wrote: >> That said I think this is not as important as other, similar, changes >> we could make. For instance, the term "master" is used _along with_ >> "slave" in manual/terminal.texi, and I fully intend to rewrite that >> chapter to eliminate that terminology as soon as I find the time. >> Anyone want to beat me to it? > > No, but please include me in the discussions. It would be good if libc > and man-pages could find common terminology. > > But I agree also with Joseph that the scope is wider and we should > think about what terminology POSIX might (be convinced to) switch to. > > Unlike Florian, I'm not excessively attached to the need to settle on > a name that starts with 's'. I think it might be too easy to get into > knots trying to find names that match 'm' and 's', and one should at > least allow for the possibility of good names that don't fit with > those letters; what would be best, IMO, is names that "feel right". > That said, Paul's mail landed while I was composing this, and I find > "main" and "subsidiary" are not awful as ideas, though "main" feels a > little contrived. I agree. It is an auto-proposition that the letters ptm/pts actually match the terminology used. You can retrofit the acronym if *any* of the letters are used in the right order. -- Cheers, Carlos.