state of libstdcxx_so_7-branch
Paolo Carlini
pcarlini@suse.de
Mon May 7 09:03:00 GMT 2007
Hi,
and sorry for replying late...
> One of the things that was learned from the libstdcxx_so_7-branch was
> that unless things are merged pretty regularly, things can get really
> hard.
>
> I would suggest some kind of schedule, or merging libstdc++ and gcc
> sources separately.
>
> In addition, I would suggest putting up all the tools for merging, or
> posting commands and establishing best practice for this (written down
> somewhere), or somehow collecting all this info, so that this
> responsibility can be handed around so that just one person isn't
> stuck with it all the time.
>
> Paolo probably has some insights here.
Thanks Benjamin, but I just totally agree with you, really. Maintaining
such a branch means a lot of work, while mainline is still actively
developed and merges are not trivial.
>> If this is the way to go, and I think it is, then I'm certainly not
>> the best person to make this change. Someone with a better
>> understanding of the configure logic, header install process, etc.
>> should handle the initial setup of libstdc++-v4.
>
> I'm willing to tackle this but let's get the post-Oxford mailing
> deadline out of the way first.
>
> It might also be wise to finish up the exploration of how to do merged
> traits. Paolo, do you want to give that a try?
You mean, the traits thing, right? I agree it has very high priority. I
want to help, yes, only I'm not sure about the timings, I have a few
pending deadlines (e.g., complete __is_convertible_to in the C++
front-end)...
Thanks,
Paolo.
More information about the Libstdc++
mailing list