Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlMKl-00047S-Te for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jun 2020 00:53:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jlMKj-0005XG-BQ for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jun 2020 00:53:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlMKj-0005X9-02 for pgsql-hackers@lists.postgresql.org; Wed, 17 Jun 2020 00:53:41 +0000 Received: from mail-qt1-x841.google.com ([2607:f8b0:4864:20::841]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jlMKb-00046L-B7 for pgsql-hackers@postgresql.org; Wed, 17 Jun 2020 00:53:39 +0000 Received: by mail-qt1-x841.google.com with SMTP id k22so288489qtm.6 for ; Tue, 16 Jun 2020 17:53:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=b4Fn8a2YMkbChR0I/F6Gse8Sgd/ppru8vBINiiyDuRI=; b=tW73GXl/jn7RjQ3Hf9xGhszZ9q7sXTWZD2n3sokwdggCqVkCldxxy9hftc9zeew4BB DwVBYwggVrPFp9NOgp9ZRdQRDVpe+K69hQVR/bI/LtoqGhdkM6IIDMIgUsvDXOuNf5Iu x9jI6daE3ONoCOgypk5gaWsJRBEZlArQfKMwx6sVg4NJoZmnLSp3XFzm5iEp3oHHuXJi hZZq6pYJnDA9Q0hYBAxKt+mLbf+L8OTqoFVnxgJqVW4onONll+7BzW/mxpc6mP2r5fwv MyyKPOEvmHTueeLMtvoBcGO3UlcvO6NeiK8LfwmQ/e42Gby9EsgwmGhfSnv3L+EP5TD8 5y6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=b4Fn8a2YMkbChR0I/F6Gse8Sgd/ppru8vBINiiyDuRI=; b=jfoB7cYrVGMzGKC0kwko2DEYAGuGNvnWBICa5QyExnL4CVWp+vDNEnEKADxBzf1WiI 3cDo3NS2ZCWI7R+H5ubA932TcbTRmaJX2ght122/TXA+ho9fhnk7CBSMZgrI7YErBuxQ 8mHySRw1rdPRO/Opz+c4I8V4yZ5zsvfVMtN+F0k3cXZT5vnI9kFAb4cPGOEcxkGOtleY xjsfC5+H4h3M6SDu66e8BcGOzzxxOR2lK8/3zHN9iFSewL4HENn1RyA6Pr1nuZlL/7ai cYzZXRBM6HDfvBLDVb6gMbsDwpd4cYLTbLK5XVccyN1GVcsAMfCMebTRYKfMQuAtjXPR M0Ig== X-Gm-Message-State: AOAM533YrEYFelZz8YXNTrSCCxoEvYkWlswqL5NqsMnSyMAe+rD46Vns cwd5PaDIHvMB4V2mFKseYg+MTw== X-Google-Smtp-Source: ABdhPJx9sWgW0565EEo50/BF9KVKMfmjtgS2dOtkxPLDMgy+oxRVlNRvHua3dvB2RxngdUJiUvwmWQ== X-Received: by 2002:ac8:4b58:: with SMTP id e24mr24712346qts.278.1592355211606; Tue, 16 Jun 2020 17:53:31 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id b188sm15287414qkc.30.2020.06.16.17.53.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jun 2020 17:53:31 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 2F3AC2A39CE; Tue, 16 Jun 2020 20:53:29 -0400 (-04) Date: Tue, 16 Jun 2020 20:53:29 -0400 From: Alvaro Herrera To: Tom Lane Cc: Andrew Dunstan , Andres Freund , pgsql-hackers@postgresql.org Subject: Re: language cleanups in code and docs Message-ID: <20200617005329.GA14742@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1406831.1592351744@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Jun-16, Tom Lane wrote: > Andrew Dunstan writes: > > On 6/15/20 2:22 PM, Andres Freund wrote: > >> 2) 'master' as a reference to the branch. Personally I be in favor of > >> changing the branch name, but it seems like it'd be better done as a > >> somewhat separate discussion to me, as it affects development > >> practices to some degree. > > > I'm OK with this, but I would need plenty of notice to get the buildfarm > > adjusted. > > "master" is the default branch name established by git, is it not? Not > something we picked. I don't feel like we need to be out front of the > rest of the world in changing that. It'd be a cheaper change than some of > the other proposals in this thread, no doubt, but it would still create > confusion for new hackers who are used to the standard git convention. Git itself is discussing this: https://public-inbox.org/git/41438A0F-50E4-4E58-A3A7-3DAAECB5576B@jramsay.com.au/T/#t and it seems that "main" is the winning choice. (Personally) I would leave master to have root, would leave root to have default, would leave default to have primary, would leave primary to have base, would leave base to have main, would leave main to have mainline. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services