I've been working trying to understand Git a little better and trying to evaluate whether it is appropriate for LFS to migrate.
What I've done is to copy the alfs repository to anduin and work with that copy. Note to Pierre: nothing has been changed on the lfs server. I had to reorganize the repo for best results because the process of migrating is fairly complex and time consuming. I chose ALFS because the repo is much smaller than either the LFS or BLFS. I also created a new name for the server: git.linuxfromscratch.org. What I suggest is for -devs to get a copy of this modified repo and play with it. The command is: git clone git://git.linuxfromscratch.org/alfs.git After download, you can 'cd alfs' and look around. A comparison of svn and git commands is at http://git-scm.com/course/svn.html The one thing you can't do right now is a 'git push' to update the remote repo. Otherwise most commands should work. If you want to be able to push changes back to the server, send me your ssh public key and I can set that up for you. If we do end up deciding (and that is far from a done deal) to use git, there will be a lot of work because a lot of scripts depend on svn. The editor's guide will need to be updated and the web pages too. The biggest issue with git from my perspective is the learning curve. It's a completely different paradigm. It seems to me that it takes more commands to do things than with svn, but the main advantages are that it brings us up to what so many other open source projects are using and that it makes merging easier for coordinating the systemd version of lfs with the main version. This would be especially important if we want to create a systemd version of BLFS. I'm sending to both the lfs and blfs mailing lists, but please reply to just the lfs list to keep the thread together. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
