Re: [RFA] Re: [RFC][patch 1/9] initial Python support

[Thiago Jung Bauermann <bauerman@br.ibm.com>]

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