Building additional binaries

[Bernhard Fischer]

On Wed, Jul 05, 2006 at 07:59:55PM -0400, Rob Landley wrote:
>On Wednesday 05 July 2006 1:04 pm, Mike Frysinger wrote:
>> On Wednesday 05 July 2006 11:27, Rob Landley wrote:
>> > On Wednesday 05 July 2006 2:40 am, Mike Frysinger wrote:
>> > > On Wednesday 05 July 2006 00:51, Jason Schoon wrote:
>> > > > He is building in bFLT format (uClinux binary flat format) rather
>> > > > than ELF. Seems like a worthwhile and hopefully not insurmountable
>> > > > task.
>> > >
>> > > it's already integrated into the build system, Shaun just wants to let
>> > > the user add it to the default build list
>> >
>> > Sigh.  For 1.4 or so I'm definitely creating my own git repository.
>>
>> that statement doesnt make any sense considering the context
>
>A general longing for better tools.
>
>I want to be aware of what's in the repository.  I want to make it so that 
>people can maintain their own trees and that merging entire sequences of 
>patches between them is easier.  (That way, you or Bernhard can queue up a 
>dozen patches at a time and I can review 'em as I merge them, without it 
>turning into a bunch of conflicts that I have to fix up by hand in order to 
>actually merge.)

Rob, trunk is in a really bad shape IMO. I'm feeding my
fixes/enhancements to a separate branch, so i have a working base to use
and develop with. I'll refrain from checking code-changes into trunk for
now, so i will not interfere with anything you may decide to change
there.

I'm regularly pulling worthwile stuff off trunk into my branch now as i
want the branch to contain less bugs than trunk does. Regularly as in
it has approximately the feature-set of the 1.2.0 release (plus a bit)
and has a couple of fixes i had to do to bring it back to something i
could deal with.

My hope is that this approach will let you clean out your backlog and
get something useful done which works, without you having to deal with
somebody else (at least me) introducing conflicts.
>
>Rob
>-- 
>Never bet against the cheap plastic solution.
>_______________________________________________
>busybox mailing list
>busybox at busybox.net
>http://busybox.net/cgi-bin/mailman/listinfo/busybox
>