Hi Folks Am 24.03.2015 um 12:38 schrieb Erich Titl: ..
> > I don't know, if we can use this to just give access to the current or > stable files. I did some local experiments > > mega@leafbuilder:~/leaf/devel/packages$ du -s . > 5961104 . > > mega@leafbuilder:~/leaf/devel/packages$ git branch > master > * stable > mega@leafbuilder:~/leaf/devel/packages$ ls > i386 tools version > > mega@leafbuilder:~/leaf/devel/packages$ git checkout master > Checking out files: 100% (3087/3087), done. > Gewechselt zu Branch 'master' > Ihr Branch ist auf dem selben Stand wie 'origin/master'. > mega@leafbuilder:~/leaf/devel/packages$ ls > 3_1 4_0 4_1 4_2 4_3 5_0 5_1 stable tools > mega@leafbuilder:~/leaf/devel/packages$ du -s . > 6605796 . > > This leads me to believe that by using branches we could get a more > granular access to the files. GIT appears to be quite efficient to > manage it's branches, which makes me believe it either handles the > inodes directly or does some link management. In either case there > appears not to be a big overhead. > > I have not yet written this back to sourceforge, as I would like to have > some feedback on this aproach. Would anyone comment on this please. Does anyone have experience with the html interface of git? Thanks Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
