From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20010 invoked by alias); 15 Jul 2008 18:33:55 -0000 Received: (qmail 19841 invoked by uid 22791); 15 Jul 2008 18:33:54 -0000 X-Spam-Check-By: sourceware.org Received: from igw1.br.ibm.com (HELO igw1.br.ibm.com) (32.104.18.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 Jul 2008 18:33:33 +0000 Received: from mailhub1.br.ibm.com (mailhub1 [9.18.232.109]) by igw1.br.ibm.com (Postfix) with ESMTP id 019E132C160 for ; Tue, 15 Jul 2008 15:06:03 -0300 (BRT) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m6FIWd4N1953972 for ; Tue, 15 Jul 2008 15:32:50 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m6FIWPLR023165 for ; Tue, 15 Jul 2008 15:32:28 -0300 Received: from [9.18.238.102] ([9.18.238.102]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m6FIWOKB023124; Tue, 15 Jul 2008 15:32:24 -0300 Subject: Re: [RFA] Re: [RFC][patch 1/9] initial Python support From: Thiago Jung Bauermann To: tromey@redhat.com Cc: gdb-patches ml In-Reply-To: References: <20080429155212.444237503@br.ibm.com> <20080429155304.288626880@br.ibm.com> <20080528205921.GA2969@caradoc.them.org> <20080615181833.uxmo25mg0kko40kw@imap.linux.ibm.com> <1216107418.14956.27.camel@localhost.localdomain> Content-Type: text/plain Date: Tue, 15 Jul 2008 18:33:00 -0000 Message-Id: <1216146743.14956.56.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2008-07/txt/msg00307.txt.bz2 On Tue, 2008-07-15 at 11:19 -0600, Tom Tromey wrote: > How can we change our development process in git to make this work > simpler for you? Thanks for asking. :-) Well, my suggestion is to stop using the git repo and move everything here to the mailing list. After the 1st (initial python support) and 2nd (export values) patches are accepted (and they seem to be close), I don't see a reason to keep working in a separate branch. But if you prefer to continue to use it, we can think of improvements to the process (like rebasing to a clean CVS HEAD, for instance). My current idea is to produce a refreshed version of each of the patches that I posted in the original python series, with all the changes that went into the python-revisited branch since they were first posted (I already have that, with commits up to yesterday in my local python-patches branch). Then I can either post the patches here to the list, or (since I'm not sure if they are ready to be approved) send you a patches/ directory suitable for use with quilt, and from there each of us drive his own patches to acceptance (there are one or two which have both our names in the changelog. We can have a duel at sunset to decide about those). WDYT? -- []'s Thiago Jung Bauermann Software Engineer IBM Linux Technology Center