Braids wrote:Snacko wrote:Any git repository = clone if it's not the original (but clone == original in content). Those at gitorious are personal server side clones which everyone can see and clone from. If you just clone locally then others would need to access your computer to clone from.
so, a server side clone is like a public personal branch?
do people who create server side clones also have to clone locally to use EGit?
You can have an infinite number of branches in your server side clone. It's more like a whole copy of svn repository along with your changes / branches.
In git you can have any number of remote repositories that you want to pull from /push to.
In Egit terms:
In Window>Show view>Git repository
Now find Remotes node and expand it.
You should see one subnode 'origin', which is the default name for a remote reposiotory.
To add a new remote just right click on Remotes node and select Create Remote.
Now configure the address for your remote gitorious clone. You can define which if any tags / branches you want to push or map to.
Now you should see a new subnode under Remotes. You can fetch / push to your other repository now.
You can add as many remote repositories as you need to.
You can configure the pushes for example that you only push some branches to your private repo and only master to the main repo. If you have questions how to set this up I can write this too.
As a quick disclaimer, you need to push changes from main repository to your private, because it wont update automagically.
do people who create server side clones also have to clone locally to use EGit?
Yes (if you mean clone main repo), because the server side clone is a bare repository just like the main repo. Also as noted before you have to update your clone yourself. Data in the private clone stays at the revision you cloned at.
Also if you ever use rebase feature of git don't publish the branch you rebase to general public. This leads to anyone who clones your repo will have a corrupted git index which can't be easily fixed. The standard procedure is to reclone your whole repo.