Re: busybox v. 1.18.3

2011-02-23 Thread Otavio Salvador
On Wed, Feb 23, 2011 at 20:22, Michael Tokarev wrote: ... > I'm refreshing all patches now as suggested by Cristian Greco, > now against 1.18 tree, -- in order to make it buildable again. Good. I would like to thank you and Christian for this works. > My first attempt, let's hope subsequent atte

Re: busybox v. 1.18.3

2011-02-23 Thread Michael Tokarev
23.02.2011 19:43, Otavio Salvador wrote: > On Wed, Feb 23, 2011 at 07:51, Michael Tokarev wrote: > ... >> As I mentioned already, there was no _config_ changes in >> this 1.18 package compared with 1.17, so the only possible >> changes are bugs introduced in busybox itself, but there >> should - h

Re: busybox v. 1.18.3

2011-02-23 Thread Otavio Salvador
On Wed, Feb 23, 2011 at 07:51, Michael Tokarev wrote: ... > As I mentioned already, there was no _config_ changes in > this 1.18 package compared with 1.17, so the only possible > changes are bugs introduced in busybox itself, but there > should - hopefully - be none, and even if there are such >

Re: busybox v. 1.18.3

2011-02-22 Thread Michael Tokarev
[Replying to an old(ish) email which I didn't notice somehow] 16.02.2011 00:41, Joey Hess wrote: > Michael Tokarev wrote: >> this is first refresh of new upstream (1.18) branch, >> currently at 1.18.3. > > Speaking of upstream, since busybox upstream is in git, it > can easily be merged into our

Re: busybox v. 1.18.3

2011-02-16 Thread Otavio Salvador
On Tue, Feb 15, 2011 at 21:41, Joey Hess wrote: > Michael Tokarev wrote: >> this is first refresh of new upstream (1.18) branch, >> currently at 1.18.3. ... > Merging that with your branch allows it to build > without needing to faff with tarballs. Would it make sense > to include upstream source

Re: busybox v. 1.18.3

2011-02-15 Thread Joey Hess
Michael Tokarev wrote: > this is first refresh of new upstream (1.18) branch, > currently at 1.18.3. Speaking of upstream, since busybox upstream is in git, it can easily be merged into our repository. For example: git remote add upstream git://git.busybox.net/busybox git pull upstream git merge

Re: busybox v. 1.18.3

2011-02-15 Thread Michael Tokarev
15.02.2011 10:43, Michael Tokarev пишет: > 15.02.2011 09:08, Christian PERRIER wrote: >> Quoting Michael Tokarev (m...@tls.msk.ru): >> >>> size on i386: >>> textdata bss dec hex filename >>>40344917908988 414227 65213 busybox-1.17.1 >>>42031617878984

Re: busybox v. 1.18.3

2011-02-14 Thread Michael Tokarev
15.02.2011 09:08, Christian PERRIER wrote: > Quoting Michael Tokarev (m...@tls.msk.ru): > >> size on i386: >> textdata bss dec hex filename >>40344917908988 414227 65213 busybox-1.17.1 >>42031617878984 431087 693ef busybox-1.18.3 > > (cc'ing you,

Re: busybox v. 1.18.3

2011-02-14 Thread Christian PERRIER
Quoting Michael Tokarev (m...@tls.msk.ru): > size on i386: > textdata bss dec hex filename >40344917908988 414227 65213 busybox-1.17.1 >42031617878984 431087 693ef busybox-1.18.3 (cc'ing you, still...not sure if you're subscribed to -boot) Could

Re: busybox v. 1.18.3

2011-02-14 Thread Michael Tokarev
14.02.2011 22:44, Michael Tokarev wrote: > Please pull from > > git://git.corpit.ru/busybox-debian.git bb-1.18 > > this is first refresh of new upstream (1.18) branch, > currently at 1.18.3. > > All applicable patches refreshed, all merged patches > are dropped (all verified - yes, they were al

busybox v. 1.18.3

2011-02-14 Thread Michael Tokarev
Please pull from git://git.corpit.ru/busybox-debian.git bb-1.18 this is first refresh of new upstream (1.18) branch, currently at 1.18.3. All applicable patches refreshed, all merged patches are dropped (all verified - yes, they were all merged, some slightly differently), configs refreshed but