On 05/08/14 02:17, Ilya Enkovich wrote:
Right. Richi explicitly wanted the entire set approved before staging in
any of the bits.
I thought it would be useful to have approved codes in the trunk to
reveal some possible problems on earlier stages. It also requires
significant effort to keep everything in consistency with the trunk
(especially when big refactoring happens) and having some parts
committed would be helpful. Will keep it in a branch for now but let
me know if you change your mind :)
I understand -- my preference would to be go go ahead with the stuff
that's already been approved, mostly for the reasons noted above. But
with Richi wanting to see it go in as a whole after complete review I
think it's best to wait. While we could argue back and forth with
Richi, it's not a good use of time.
It's in the queue of things to look at, but it's a deep queue at the moment.
Thanks for keeping an eye on it! Hope this year we can start sooner
and have enough time to make it with no hurry.
Agreed.
BTW, are you or any colleagues coming to the Cauldron this year in
Cambridge? It's often helpful to get together and hash through issues
in person. I think most of the core GCC developers will be there.
jeff
