The ADI specific GNU toolchain, u-boot and buildroot Lniux distribution projects keep their source code in GIT. While the ADI specific Linux libraries, applications and test suites are kept in Subversion (SVN).
git is a fast distributed scm that is used in many open source projects but most notably, the Linux kernel. Unlike SVN/CVS, it has no centralized repository.
All of the blackfin Linux projects except for the obsolete uClinux-dist switched to the new GIT repositories at http://blackfin.uclinux.org/ from the SVN repositories.
The sub directory will be called “u-boot”:
$ git clone git://git.code.sf.net/p/adi-toolchain/blackfin toolchain
$ git clone git://git.code.sf.net/p/adi-u-boot/code u-boot
$ git clone git://git.code.sf.net/p/adi-buildroot/code buildroot
Subversion is touted as a replacement for CVS.
An online book is available http://svnbook.red-bean.com.
The source code for subversion itself is found at its homepage http://subversion.tigris.org.
Most popular distributions already have packages available for you.
$ svn checkout svn://svn.code.sf.net/p/adi-openapp/code/trunk adi-open-app
$ svn info
$ svn info svn://svn.code.sf.net/p/adi-openapp/code/branch/2008R1
$ svn log -v svn://svn.code.sf.net/p/adi-openapp/code/branches/2008R1 | less
$ svn update
$ svn update -r 5316
$ svn st 'A' Added 'C' Conflicted 'D' Deleted 'I' Ignored 'M' Modified 'R' Replaced '?' item is not under version control '!' item is missing (removed by non-svn command) or incomplete
$ svn log -v | less
$ svn diff
$ svn commit
Say you want to checkout a repository from a fast local mirror and then use that checkout to commit to the original repository (so you don't need to check things out twice from different servers). SVN provides a method for switching the repository your local checkout works against.
$ svn co svn://some.fast.mirror/project/trunk project $ cd project $ svn switch --relocate svn://some.fast.mirror/project/trunk svn://some.slow.server.to.commit.to/project/trunk
Once you've made your checkins, you can of course switch back to the fast mirror by doing the inverse of the above switch command.
While CVS requires you to use magic commands to create tags and branches, SVN has actual directories in the top level.
So to create a branch in svn, you would:
$ svn cp trunk branch/2013R1 $ svn commit -m 'add new 2013R1 branch' branch/2013R1
And to tag a release:
$ svn cp branch/2013R1 tags/2013R1-RC1 $ svn commit -m 'tag new 2013R1-RC1 release' tags/2013R1-RC1
Here's a quick reference for common commands and their counterparts in CVS, SVN, and git. Most commands are (purposefully) pretty much the same, but the little details are what nag you.
|Checkout a repository||cvs -d <cvsdir> co <cvs module>||svn co <svn url> <local path>||git clone <git url> <local path>|
|Update a repository||cvs up||svn up||git pull|
|See changed files||cvs up||svn st||git status|
|Revert local changes||cvs up||svn revert||git checkout|
|Accessing revisions||cvs … -r old_rev -r new_rev …||svn … -r old_rev:new_rev …||git old_rev..new_rev|
|Generating diffs||cvs diff file||svn diff file||git diff file|
|Viewing history||cvs log file||svn log file||git log file|
|Adding files||cvs add file||svn add file||git add file|
|Removing files||cvs rm file||svn rm file||git rm file|
|Rename a file||(no cvs equivalent)||svn mv <old file/path> <new file/path>||git mv <old file/path> <new file/path>|
|Copy a file||(no cvs equivalent)||svn cp <old file/path> <new file/path>||(no git equivalent)|
|Commit changes||cvs commit -m 'log message' file||svn commit -m 'log message' file||git commit -m 'log message' file|
Other than per-project repositories, people with accounts may create as many per-user git or svn repos as they like. However, the interface is command line only (no website interface to this).
By default, the repo is created with permissions such that only you may access it (read or write). If you want, you can change the permissions to let any one read it (but you still are the only one who can write it).
The interface is simple (to use the svn version, simply change
$ ssh $USER@sources.blackfin.uclinux.org git-publish -h Usage: git-publish <-c|--create> <repo> <description> Usage: git-publish <-p|--make-public> <repo> Usage: git-publish <-P|--make-private> <repo> Usage: git-publish <-S|--make-semi-public> <repo> Usage: git-publish <-d|--set-desc> <repo> <description> Usage: git-publish <-r|--remove) <repo> Public: world readable (git/rsync) and via http viewgit Semipub: world readable (git/rsync) but not via http viewgit Private: readable only by you
So to create a new git repo and then check it out, you do:
$ ssh $USER@sources.blackfin.uclinux.org git-publish -c foo $ git clone ssh://$USER@sources.blackfin.uclinux.org/git/$USER/foo.git
Or for svn:
$ ssh $USER@sources.blackfin.uclinux.org svn-publish -c foo $ svn co svn+ssh://$USER@sources.blackfin.uclinux.org/svn/users/$USER/foo
The git interface has a gitweb interface, but there is nothing for svn.