# [PATCH] Cogito README: add a block describing team workflow with git+ssh

2 messages from 2005-10-21 to 2005-10-21. Participants: Martin Langhoff, Petr Baudis.
Thread: https://gitlist.dev/t/2181

## Martin Langhoff, 2005-10-21 05:34

Subject: [PATCH] Cogito README: add a block describing team workflow with git+ssh
Message-ID: <11298728883894-git-send-email-martin@catalyst.net.nz>
URL: https://gitlist.dev/e/11298728883894-git-send-email-martin%40catalyst.net.nz

```
This is a resend, with a silly typo (chgroup/chgrp) fixed.

---

The README doesn't talk about teams with "peer" access to a shared repo.
It took me a while to figure our the /right/ way to do it. Document for
future generations and general happiness.

---

 README |   35 +++++++++++++++++++++++++++++++++++
 1 files changed, 35 insertions(+), 0 deletions(-)

applies-to: 06a96ef8bc54639d5e42319c86cac2d812327cf0
1217193450bf9ae108af2341f1383eb496d31b62
diff --git a/README b/README
index 70908bc..fb87adb 100644
--- a/README
+++ b/README
@@ -268,6 +268,41 @@ Note that we gave only a glimpse to the 
 - merging (`cg-merge`), moving your tree to an older commit (`cg-seek`),
 pushing (`cg-push`), etc.
 
+Using Cogito for Team Work
+--------------------------
+
+A small team with SSH access to a shared server can use Cogito in a way 
+similar to traditional CVS over SSH. 
+
+If you are bootstrapping the project, and you have a local Cogito working copy,
+you must set up the shared repository and push a local head to it.
+
+To set up the shared repository, for example in 
+remoteserver:/var/git, login to the remote server and do
+
+        $ umask  002
+        $ mkdir /var/git
+        $ chgrp gitcommit /var/git
+        $ chmod  2775 /var/git
+        $ mkdir -p /var/git/projectname.git
+        $ GIT_DIR=/var/git/projectname.git git-init-db
+        
+Note: All the developers with "commit" access must belong to the gitcommit
+group and have a 002 umask on the remote server.
+
+Going back to your Cogito working copy, run 
+
+        $ git-push  remoteserver:/var/git/projectname.git master branchname
+
+Now your other teammembers can start working with you, doing
+
+         $ cg-clone git+ssh://remoteserver/var/git/project.git#branchname localdir
+
+And when they are ready to push their work onto the shared repository, just do
+
+         $ cg-update
+         $ cg-push
+
 
 Understanding GIT branching and merging
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---
0.99.8.GIT

```

## Petr Baudis, 2005-10-21 15:14

Subject: Re: [PATCH] Cogito README: add a block describing team workflow with git+ssh
Message-ID: <20051021151451.GH30889@pasky.or.cz>
URL: https://gitlist.dev/e/20051021151451.GH30889%40pasky.or.cz
In-Reply-To: <11298728883894-git-send-email-martin@catalyst.net.nz>

```
Dear diary, on Fri, Oct 21, 2005 at 07:34:48AM CEST, I got a letter
where Martin Langhoff <martin@catalyst.net.nz> told me that...
> This is a resend, with a silly typo (chgroup/chgrp) fixed.

It was missing the signoff, but I worked that around by taking your
original patch from the end of September. ;-)

> The README doesn't talk about teams with "peer" access to a shared repo.
> It took me a while to figure our the /right/ way to do it. Document for
> future generations and general happiness.

Thanks. The long sequence of permissions setup inspired me to adding
cg-admin-setuprepo which automates that. I also changed the git-push
to cg-push. Please review the final result.

Thanks,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.

```