Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id iA1JUqoJ022033 for ; Mon, 1 Nov 2004 19:30:53 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id 6FF2076E9E for ; Mon, 1 Nov 2004 19:30:53 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1COi1G-0007C9-6j for migo@homemail.com; Mon, 01 Nov 2004 14:39:10 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1COi00-0006xZ-Rg for gnu-arch-users@gnu.org; Mon, 01 Nov 2004 14:37:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1COhzz-0006xG-Ca for gnu-arch-users@gnu.org; Mon, 01 Nov 2004 14:37:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1COhzy-0006x4-Vs for gnu-arch-users@gnu.org; Mon, 01 Nov 2004 14:37:51 -0500 Received: from [204.152.189.135] (helo=kechara.flame.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1COhre-0000E4-88 for gnu-arch-users@gnu.org; Mon, 01 Nov 2004 14:29:14 -0500 Received: (qmail 13392 invoked by uid 323); 1 Nov 2004 19:29:09 -0000 To: Thomas Lord Mail-Followup-To: gnu-arch-users@gnu.org Subject: Re: [Gnu-arch-users] Potential flaw in patch-log pruning in proposal References: <20041025210724.GA19744@merconline.com> <87fz3to83f.fsf@flame.org> <200411011834.iA1IYNGS030540@xl2.seyza.com> From: Matthew Dempsky Date: Mon, 01 Nov 2004 13:30:22 -0600 In-Reply-To: <200411011834.iA1IYNGS030540@xl2.seyza.com> (Thomas Lord's message of "Mon, 1 Nov 2004 10:34:23 -0800 (PST)") Message-ID: <87y8hlmkoh.fsf@flame.org> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: gnu-arch-users@gnu.org X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1447 Lines: 35 Thomas Lord writes: > > From: Matthew Dempsky > > > One other thing to consider about merging submission branches is that > > they all add a CONTRIBUTION-LOG file which would surely conflict > > unless you made sure to delete this after merging. > > > (Whether to interpret this as a problem with the proposal or the idea > > of development lines merging submission branches I'm not sure about > > yet.) > > It's deliberate. The merging you do to merge a submission branch is, > in effect, a higher-level merge command than ordinary 'star-merge'. > You have to deal with 'CONTRIBUTION-LOG' and with pruning patch logs. > Eventually, this higher-level command should be built-in to 'tla' but, > for now, please just write yourself a little shell script. Right, I am using a script to automate that part. In that email, however, I was referring to people who are simply updating their trees (e.g. jblack, abentley, etc.) wrt the submission branches that have been merged into mainline now. They would want to be able to star-merge or replay those branches as well in case any changes were made in the submission branch (patch fixes or conflict resolution stuff). _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/