Thanks for the feedback. It seems like there's a mix of interest so I'll plug on. See the git-migration directory in the subversion2git branch ( https://github.com/lyda/Linux-From-Scratch/tree/subversion2git ) for more info.
I did a git-svn fetch on the repo I cloned from github and got the latest changes from the svn tree. I was then able to push them to the github repo. So the github repo is a viable way to track the subversion tree. I'm impressed by the git-svn system - though I have yet to attempt a commit so we'll see. I was thinking it would be interesting to put all the sources LFS uses in with the sources for the book. That way you could just checkout the branch for a given version and then you'd have everything you needed right at your fingertips. Yes, the sources are large, but git does compression and duplicate detection. How much of an affect would that have? So last night I untarred all the tarballs in the lfs-packages-VER.tar tarballs for versions 6.7 and 6.8 and stuck them in a git repo (in a 6.6 and 6.7 directory). The resulting .git directory is 411M after a git gc --aggressive --prune; the resulting 6.6 and 6.7 directories were 1.9G each. That's a pretty impressive compression ratio since the two tarballs are 567M combined. However it still seems too huge. I'll try putting in 6.6 to see if the space savings increase further but I don't think it's a good idea to try and put the sources in with the book git repo. Might be something to revisit when we all have fibre to the home, petabyte solid state storage, flying cars, etc. Kevin -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
