From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9243 invoked by alias); 10 Jan 2020 18:22:33 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 9219 invoked by uid 89); 10 Jan 2020 18:22:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=Our, our X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Jan 2020 18:22:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D27EF1176D0; Fri, 10 Jan 2020 13:22:30 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WcmKVbo9wAaP; Fri, 10 Jan 2020 13:22:30 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 6BB7B1176CA; Fri, 10 Jan 2020 13:22:30 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 2E90882B7F; Fri, 10 Jan 2020 22:22:26 +0400 (+04) Date: Fri, 10 Jan 2020 18:22:00 -0000 From: Joel Brobecker To: Joseph Myers Cc: Jason Merrill , Maxim Kuvyrkov , gcc Mailing List , Gerald Pfeifer , Daniel Berlin Subject: Re: GCC Git hooks Message-ID: <20200110182226.GL3313@adacore.com> References: <20190916150650.GB4945@adacore.com> <20200110180049.GH3313@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2020-01/txt/msg00141.txt.bz2 > > > Plus one further change now: if a newly created branch is in refs/heads/, > > > require it to be in refs/heads/devel/ or refs/heads/releases/ (i.e. > > > enforce a particular branch naming convention, in particular to prevent > > > mistakes where people accidentally push a branch into refs/heads/ because > > > their push configuration for user or vendor branches was wrong). > > > > I'm having a hard time understanding this requirement. > > > > You want to say that, before branch "" gets created, you want > > to verify that a branch named either "devel/" or "releases/" > > does exist? > > No. What we want to ensure is that people don't accidentally create a > branch called refs/heads/foo when they should (by our naming conventions) > have created one called refs/heads/devel/foo or > refs/users/someone/heads/foo. Our naming conventions mean that all > branches in refs/heads/ should be called master, devel/something or > releases/something. But it's easy for someone to get a "git push" command > wrong so that it would create a badly named branch. Could you rely on the update-hook script for that? -- Joel