Really happy with cogito for inhouse teamwork, now that I've figured out cg-clone...

Just wanted to mention something that isn't in Cogito's readme, and has been crucial in making our use of cogito straightforward.

We've made the transition a few weeks ago, and we've been _really_ happy with git/cogito (over cvs and tla, our "other" SCMs). Whoever, there was something we all found ackward in how we did clone/pull/push.

The _right_ way to do for a team with git-over-ssh is:

Doing the checkout the 'right' way:
 $ cg-clone git+ssh://locke.catalyst.net.nz/var/git/project.git#branchname
localdirname

Work cycle:
 # work work work
 $ cg-commit
 $ cg-update
 $ cg-push

The README doesn't talk about teams with "peer" access to a shared repo. So I fumbled about and we were doing cg-clone using rsync (rsync protocol or over ssh), or just straight http. This made pushing back to the repo impossible with Cogito. So we were calling git-push directly, with the risk of pushing to the wrong head (only really risky for two very closely related heads, but still).

Now, I should put this into a patch to Cogito's README.... give me 5'...

martin