From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31648 invoked by alias); 23 Jan 2014 15:35:42 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 31596 invoked by uid 89); 23 Jan 2014 15:35:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 23 Jan 2014 15:35:41 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s0NFZZdO016013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Jan 2014 10:35:35 -0500 Received: from barimba (ovpn-113-85.phx2.redhat.com [10.3.113.85]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id s0NFZXJQ026867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 23 Jan 2014 10:35:34 -0500 From: Tom Tromey To: Joel Brobecker Cc: gdb-patches@sourceware.org Subject: Re: reject merges on gdb release branches? References: <20140122051133.GB4762@adacore.com> <20140123055758.GG4762@adacore.com> Date: Thu, 23 Jan 2014 15:35:00 -0000 In-Reply-To: <20140123055758.GG4762@adacore.com> (Joel Brobecker's message of "Thu, 23 Jan 2014 09:57:58 +0400") Message-ID: <87r47y4soq.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2014-01/txt/msg00904.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: >> At the moment, it appears that this can only be done by adding >> a "BRANCH_NAME = true" line in the repository's config file. >> I can do that. Joel> OK, given the positive feedback, this has now been done. The syntax was slightly off; I got an error from a push. When I corrected it I learned that git doesn't allow "." in the name of a config variable. So, if we want to do this we'll have to modify the "update" script directly; either by adding the branch names there or by changing the config variable syntax. I don't have time to do this right now, sorry. In the meantime I've reverted to the status quo ante, seeing no other choice. Tom