Depending on whether you simply want to test and follow Amarok development, write the occasional patch, or are an Amarok developer, the steps to use the repo are different.
git clone git://gitorious.org/amarok/amarok.git
This creates an 'amarok' directory. cd into that and use it like normal. And when you want to update:
will download the new changes.
You can use the method above, make your changes, then do 'git diff' to create a patch like normal. Or you could use the following rules to create your own fork of Amarok with the additions you would like to request to merge. This makes it easier for Amarok Developers to track your changes and is better for more complicated patches.
git clone email@example.com:~yourname/amarok/yourname-clone.git ...work on this checkout - follow the normal development workflow... push your changes to gitorious
git remote add upstream firstname.lastname@example.org:amarok/amarok.git
git pull upstream master
People with KDE-SVN accounts als should do the following:
Gitorious has one address for cloning, and another for pushing. The pushing address can be used for cloning, so the easy thing to do is just use that.
git clone email@example.com:amarok/amarok.git
This will create a directory 'amarok'. cd into that and start developing!
90% of the time this is all that is needed:
git pull #update to latest code #edit code, build, it works! git status #to check if you want to commit all the modified files git commit -a #the -a option commits all modified files. use git add to select them individually git push
The Git Parable: Background information that will help you understand git and distributed revision control systems in general
Git to SVN crash course 5 minute introduction to git for experienced SVN users