From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93433 invoked by alias); 10 Jan 2020 18:24:41 -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 92790 invoked by uid 89); 10 Jan 2020 18:24:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:812, Our, our X-HELO: esa3.mentor.iphmx.com Received: from esa3.mentor.iphmx.com (HELO esa3.mentor.iphmx.com) (68.232.137.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Jan 2020 18:24:39 +0000 IronPort-SDR: saaN0s6gnJrhb79DzTgz6Y2aRXtn6aM7gI8/qY8f6ulz98ErU+UGMMMK10VTqSetDDP8iwXZNZ +6SYUxb/rhWvMsxE5bugJjJ8LlgPyHzo27ItPdgJ4gIdddkqsy19v+JO8RXjOLQB36/CoSEWit eoLFeE9KEYMW3dCTIvUes5/c+dESiUSf3o25ds8U3mHyTmYXweo2tKCWSWXleKge9TloLkyikA CZnccdmItPAnEzqzd5Cj6A8Dett3Gw+e/ZQzbQg08BSLr96hdovbKxQhCXBfIyNkJTO7JsaEeV EXs= Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa3.mentor.iphmx.com with ESMTP; 10 Jan 2020 10:24:38 -0800 IronPort-SDR: f7I35vUyZiyJCt7FAVhIOjoaRlpcj/QeEb/V6LjAIj2VER+p2BtZsufCi02oV0f3yZgnYlTmEj amcZfgqyfjmnVQWHcIpwFEWQSnPdCbjZ2qIilf2hyiQQJ8KvQ9wmAtgso3Gc3SLg0bsC81JHPt nnkhO5raFU1JOs4kOgeIlZth/iFKnWNPScWctt2NM5ll491Mxza1d3ymzMTKAGInK+JFesx9PF x0ei51f8ya2wLaQFx1mMEh0FCrH3/bYRGaNkwuWEZ5OuafZVtRdFLSiMWFHApGeq0L1KHFxpkt a/E= Date: Fri, 10 Jan 2020 18:24:00 -0000 From: Joseph Myers To: Joel Brobecker CC: Jason Merrill , Maxim Kuvyrkov , gcc Mailing List , Gerald Pfeifer , Daniel Berlin Subject: Re: GCC Git hooks In-Reply-To: <20200110182226.GL3313@adacore.com> Message-ID: References: <20190916150650.GB4945@adacore.com> <20200110180049.GH3313@adacore.com> <20200110182226.GL3313@adacore.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-Path: joseph@codesourcery.com X-SW-Source: 2020-01/txt/msg00142.txt.bz2 On Fri, 10 Jan 2020, Joel Brobecker wrote: > > 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? We could, it just feels like "branch names [in refs/heads/] must match one of these naming conventions" is something fairly generic rather than extremely GCC-specific. -- Joseph S. Myers joseph@codesourcery.com