From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28919 invoked by alias); 10 Jan 2020 15:53:08 -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 28813 invoked by uid 89); 10 Jan 2020 15:53:07 -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= X-HELO: esa4.mentor.iphmx.com Received: from esa4.mentor.iphmx.com (HELO esa4.mentor.iphmx.com) (68.232.137.252) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Jan 2020 15:53:05 +0000 IronPort-SDR: h8/RegNQ1PYXuRKxgCG4nzmCrduiFrdCM4PRNFS5UwDLp+96lmmjfuXvstO72/LEizCcmw9usY BcMD9kqLbeblKcpsxXOf9143bsyECUriGnt9Xd1Gdbfk8jHLtw9QRIP/5LxWqLkk0Y54p0Q6ph opAeIGIo5vOBP3OcLyuG8OgZHrYxg9dlfgYxI35s8MfdyrfeO56NAKQ8XLRlUQB4mFa3Ml86nA qZl1IUdUmRTMV6ykiYHvV+WIBSr+GWBiYFz4LbAr6KYCs7/9vdgx/VsMi5noAUE3SAaOwFgsBG j4g= Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa4.mentor.iphmx.com with ESMTP; 10 Jan 2020 07:53:04 -0800 IronPort-SDR: VKxheseA5v7KQ4iM2/onzTFLKVZtyRqszg4HoN4LBb4iYE5ApOz8cfAHSmqRm8aTsrzhfa9rb8 OYYvsmafnpoifxQdq758kWoHqQtounXgOkMStm60/toSFY/hhDyMTqicIuexZAx6qq2oaszC1g Z0ZykPZTYQFRhjjpvnS+NIJtaCpKsaMsjX/DhnfFPk0UWwi8p1McP3fG3LEfogtFrRQVv19jqy ZWRZEelqKkE8G3dieWc3XAiqCIuz9JA71HsrnhoUla6cw+tNbW9DjkLjKRL4hcLqlr3C8jbpKR S8U= Date: Fri, 10 Jan 2020 15:53: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: Message-ID: References: <20190916150650.GB4945@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/msg00127.txt.bz2 On Thu, 9 Jan 2020, Joseph Myers wrote: > Concretely, these are the changes I'm currently using to configure the > hooks in a way I think appropriate for GCC, and it would be useful if the > hooks could support such configuration in a more generic way in future so > that we can stop using a GCC-specific patched installation of the hooks. > The following features are hardcoded that didn't seem to have a way to > configure them: 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). -- Joseph S. Myers joseph@codesourcery.com