12.02.2011 12:39, davidMbrooke пишет: > On Wed, 2011-02-09 at 23:50 +0200, Andrew wrote: >> 09.02.2011 00:05, KP Kirchdoerfer пишет: >>> Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: >>>> Is anyone able to push all the contrib packages into git? >>> All package sources has been moved into git. >>> > kp: Thank you. I know how much work that must have been. You are a hero! > >>> Pls test and give feedback if it works - or report back errors you detect >>> while building the packages. >>> >>> thx kp >>> >> All looks OK. >> I moved all sources into buildtool/repo dir, and added new server type - >> 'filesymlnk' that works like 'file' server type, but just creates >> symlinks instead of file copying - to avoid space wasting. Now all >> sources are placed into single place and it is no needed to re-download >> all of them from overloaded SF servers. >> Of course, this is a dirty hack; in future it'll be good to rewrite >> buildtool logic to work with source tree w/o copying of files (or even >> choose other building environment) - but it'll be later. >> >> P.S. I think that we should move all from bering-uclibc4 dir into root >> of git? I think that in any case we shouldn't have 2 or more branches >> paralelly into one repository - it's easy to create new repo for major >> modifications, and it's easy to maintain separate repo branches for >> minor changes. > IMHO we should retain a "bering-uclibc4" level somewhere. Git is for the > whole of LEAF, not just for bering-uclib4, and one day there will be a > bering-uclibc5...
> Right now we have a repo called "leaf" within a project called "leaf". > How about naming the repo to "bering-uclibc4" and then removing > "being-uclibc4" as a directory level within the repo? > > dMb This will be OK. I didn't create other repo when I pushed LEAF into it because SSH acces was down; now it should work. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
