Hi Phillip, Could you please stop sending millions of small patches on the assumption that small == trivial. A trivial patch is a patch that is complete in and of itself and doesn't need more patches before or after to finish solving whatever problem it is related to, and is one-time thing that only rarely is possible.
You're working on platform support for Geode platforms such as Geos and Alix2, so could you please try to get platform support fully integrated and working in a patch or patch series, and then submit the completed (or to the best of your genuine knowledge complete) patch or patch series, rather than bombarding the list with patches and getting impatient because your patches aren't applied quickly. I realize that mistakes do occur, but I'd like to see some sign you're actually making an effort to minimize unnecessary work for us, the devs, rather than just hacking on trunk with us as intermediaries. It would also make clearer what you are trying to achieve so we can best see how to integrate that with the OpenWrt philosophy and existing platforms and userbase. While I personally am interested in seeing a solution to the problem of meeting multiple embedded needs, it can't come at the expense of the core platforms and userbase. (The core of openwrt is wireless routers and access points based on commodity hardware). It would help if you told us your destination and ideas you had for a shared space with consumer hardware, and if you demonstrated that you weren't just doing many small, incomplete, and untested hacks. For platform support, I personally would like to see what you think is a (fairly) complete solution, and then work with us on the things that need to changed. That's how I got started with extroot. I didn't submit it as a series of tiny edits, but as a complete solutions. There were some more subtle bugs, and I've refactored since then, but on the whole it worked, and filled a much-requested feature in a way that fit into OpenWrt. Also, if you want me to go over some things I've learned about how to setup the builds system and image generator and environments so that I can build images based on openwrt, but with different use cases than the default openwrt (and hence different packages, configs, etc), without having to change openwrt trunk/backfire to git my goals, I should write it up on the wiki anyway. Understanding how to build images (easily) that include features/configuration that aren't appropriate as OpenWrt defaults (e.g. trunk/backfire) could help ease some tension you have with the openwrt defaults I think. (for example including large packages like openssl in the default configuration isn't necessary; you can achieve that goal with image generator and an appropriate script, without a lot of effort). Regards, Daniel -- <erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org
signature.asc
Description: PGP signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
