Re: [patches] EGLIBC 2.6 created

[Jim Blandy <jimb@xxxxxxxxxxxxxxxx>]

"Joseph S. Myers" <joseph@xxxxxxxxxxxxxxxx> writes:
> On Thu, 17 May 2007, Joseph S. Myers wrote:
>
>> Now that FSF glibc HEAD has moved to 2.7 development, I've created EGLIBC 
>> 2.6 branch as a copy of trunk.  When glibc-2_6-branch fully exists (it 
>> only exists for libc not ports at present) I'll set up imports of it.
>
> I've now set up these imports and merged EGLIBC trunk and 2.6 branch from 
> their respective FSF branches.
>
> Because of recent high load on sourceware, I've made the imports try up to 
> five times to update each CVS checkout (sleeping a minute between each 
> time); hopefully this should reduce the number of days imports don't 
> happen because of CVS updates failing.
>
> The previous comments still apply:
>
>> EGLIBC changes should now go in one of the following combinations of 
>> branches:
>> 
>> * trunk
>> * trunk and 2.6
>> * trunk, 2.6 and 2.5
>> 
>> To build with current GCC trunk you'll need EGLIBC trunk or 2.6.  Note 
>> that these now require TLS support.

What do you think it makes most sense for automated testing to use now?