From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1894 invoked by alias); 15 Jul 2008 19:03:41 -0000 Received: (qmail 1886 invoked by uid 22791); 15 Jul 2008 19:03:41 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 Jul 2008 19:03:22 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6FJ3ICl005249; Tue, 15 Jul 2008 15:03:18 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6FJ3IBf007309; Tue, 15 Jul 2008 15:03:18 -0400 Received: from opsy.redhat.com (vpn-10-3.bos.redhat.com [10.16.10.3]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6FJ3Hpw019704; Tue, 15 Jul 2008 15:03:17 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id B989B508080; Tue, 15 Jul 2008 13:03:16 -0600 (MDT) To: Thiago Jung Bauermann Cc: gdb-patches ml Subject: Re: [RFA] Re: [RFC][patch 1/9] initial Python support 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> <1216146743.14956.56.camel@localhost.localdomain> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Tue, 15 Jul 2008 19:03:00 -0000 In-Reply-To: <1216146743.14956.56.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Tue\, 15 Jul 2008 15\:32\:23 -0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00318.txt.bz2 >>>>> "Thiago" == Thiago Jung Bauermann writes: Tom> How can we change our development process in git to make this Tom> work simpler for you? Thiago> Well, my suggestion is to stop using the git repo and move Thiago> everything here to the mailing list. After the 1st (initial Thiago> python support) and 2nd (export values) patches are accepted Thiago> (and they seem to be close), I don't see a reason to keep Thiago> working in a separate branch. But if you prefer to continue to Thiago> use it, we can think of improvements to the process (like Thiago> rebasing to a clean CVS HEAD, for instance). I'm a bit reluctant to move purely to working from CVS. This will make it harder for us to work on things in concert, and will require a lot of administrative overhead as well. One thing that has been nice about this project, so far, is that we can be fairly experimental and we don't have to spend much time waiting... whereas my cvs-head-hacking experience has been pretty much the opposite. Thiago> sure if they are ready to be approved) send you a patches/ Thiago> directory suitable for use with quilt, and from there each of Thiago> us drive his own patches to acceptance (there are one or two Thiago> which have both our names in the changelog. We can have a duel Thiago> at sunset to decide about those). What if we used 'guilt' or 'StGIT' instead? I have never tried these, but they both seem to basically be git+quilt, where the patches can easily be shared. (Am I wrong about this?) This would require anyone working on the git repository to use this tool and to be careful about managing the patches. But, that would take the work off you and spread it around -- exactly what we want. Tom