This is the mail archive of the
archer@sourceware.org
mailing list for the Archer project.
Re: freshly-cut python patches
El mar, 14-10-2008 a las 07:12 -0600, Tom Tromey escribiÃ:
> >>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> Thiago> Unfortunately I wasn't able to push it yet, since I believe
> Thiago> the repo isn't configure to support forced pushs (could you
> Thiago> help with this, Tromey?)
>
> I fixed it.
Thanks, I pushed the new version now.
There are some things I need to sort out yet:
- The order of patches doesn't look right. For instance, the initial
pretty-printing patch comes before the types patch, and I believe the
former actually depends on the latter. Does pretty printing have other
dependencies, like the symbols, symtab and block patches? I saw some
fixes from you on that code, not sure if it was related to
pretty-printing or not.
- Some reordering will happen as we decide which patches to submit next.
- I'm not sure yet how to organize the pretty-printing work. A few
commits are floating around in isolation as a result of this. Initially,
I was thinking of having two patches: a "ground work and CLI pretty
printing" patch and an "MI pretty printing" patch, but it would take
some effort to make the division. Besides, you and Vladimir will
probably have to agree anyway before submitting any of the patches, so
there seems to be no benefit in the separation and I'm thinking of
making only one pretty printing patch. WDYT? Vladimir, any preference?
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center