From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19140 invoked by alias); 7 Dec 2012 21:16:38 -0000 Received: (qmail 19125 invoked by uid 22791); 7 Dec 2012 21:16:37 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 07 Dec 2012 21:16:32 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qB7LGT5l030886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 7 Dec 2012 16:16:29 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id qB7LGRa4013479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 7 Dec 2012 16:16:28 -0500 From: Tom Tromey To: Pedro Alves Cc: Eli Zaretskii , Joel Brobecker , gdb-patches@sourceware.org Subject: Re: proposal for branch patches after first release References: <20121129141415.GJ3540@adacore.com> <83wqx4v12l.fsf@gnu.org> <50B78E0C.50607@redhat.com> Date: Fri, 07 Dec 2012 21:16:00 -0000 In-Reply-To: <50B78E0C.50607@redhat.com> (Pedro Alves's message of "Thu, 29 Nov 2012 16:32:12 +0000") Message-ID: <87lid9tvf8.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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 X-SW-Source: 2012-12/txt/msg00209.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> We could also make better use of bugzilla for this. I had stated Pedro> my opinion on this Pedro> : Pedro> If people think the PR idea is too process burden for mainline, we could Pedro> require this only for fixes that go into a release branch. E.g., tag Pedro> the PRs with a special tag, e.g. "in-7.6.1". FWIW I wouldn't mind requiring a PR for each change on the branch. If this gets too burdensome then we probably should be looking at a new release anyway. Tom