On 19 October 2014 14:22, walter harms <[email protected]> wrote: > I would vote for a busybox-next (or what you call it). > A branch that easly fold back into the main but contains all > the recent patches. > That givce a clear space for experiements and makes it possible for > denis to see the reqiered changes.
Well, I am a newbie to git, but I'll give it a go seeing as nobody else has: https://github.com/stevenhoneyman/busybox I created a branch "busybox-next" and have made a start on applying patches from here (and some from OpenWRT). Either it will stay ahead or inline with upstream, or I'll remove it. I have no intention to create a fork; all upstream changes will be merged. ...if I can figure out how to use git properly :) Pull requests are welcome for any patches I might have missed. Steven. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
