On Friday 12 December 2008 21:54:24 Khem Raj wrote: > On (13/12/08 03:35), Denys Vlasenko wrote: > > On Saturday 13 December 2008 00:53, Khem Raj wrote: > > > On Fri, Dec 12, 2008 at 3:40 PM, Denys Vlasenko > > > > > > <[email protected]> wrote: > > > > Hi Carmelo, Bernhard, > > > > > > > > Having not much experience with working on a branch, > > > > I am possibly asking a stupid question, but > > > > why Carmelo is working on a branch now, after 0.9.30 > > > > is out? His code seems to be nearly ready, it does not > > > > impact much those users which would not use ntpl, > > > > so why not merge it to trunk now? There will be a bit > > > > of breakage, perhaps, but we have plenty of time > > > > to fix it before 0.9.31, right? > > > > > > We need to sync the nptl branch with trunk before merge. > > > thats what we are doing atm. > > > > Hmm, so every time I commit something to the trunk, > > I make your work harder. > > > > That's what I want to avoid. How? > > as long as the merges into branch happen > faster than the commits on trunk :) Sooner we should be good to > merge into trunk. > > Someone with mips hardware and time who can test mips nptl would be a big > help
I've got mips qemu setups for little and big endian building from source via a fully automated script I can drop arbitrary uClibc versions into. But I will never look at an svn branch. (If you want branches, git and mercurial both exist...) Rob _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
