03.02.2011 17:07, Mike Noyes пишет: > On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: >> This is quite easy: do git clone and set personal data (name/email); >> copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify >> config files (replace server names) into sources' buildenv.conf; do git >> add * and then do git commit and git push. >> After short look in leaf-commits mailing list, in current git snapshot >> only last busybox commit (update to 1.18.2) is missed. > Andrew, > Is git functional for continued development, or are further actions > necessary? It's needed to upload all required sources from old bering-uClibc into git, and it'll be good to add .gitignore with paths for temporary/work files (/source dir, /packages and so on) - to make easily compiling from buildenv from git without pushing generated binary files into it. Of course, in future it'll be good to make single GIT repository w/o need of downloading files separately - but this will be considered as improvement of usability, not as bug/1st-priority target.
------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
