From: Martin Langhoff <martin@catalyst.net.nz>
To: git@vger.kernel.org
Cc: Martin Langhoff <martin@catalyst.net.nz>
Subject: [PATCH] Cogito README: add a block describing team workflow with git+ssh
Date: Fri, 21 Oct 2005 18:34:48 +1300 [thread overview]
Message-ID: <11298728883894-git-send-email-martin@catalyst.net.nz> (raw)
In-Reply-To:
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
next reply other threads:[~2005-10-21 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 5:34 Martin Langhoff [this message]
2005-10-21 15:14 ` [PATCH] Cogito README: add a block describing team workflow with git+ssh Petr Baudis
-- strict thread matches above, loose matches on Subject: below --
2005-09-29 6:31 Martin Langhoff
2005-09-29 21:25 ` Elfyn McBratney
2005-09-29 21:52 ` Martin Langhoff
2005-09-29 22:19 ` Elfyn McBratney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11298728883894-git-send-email-martin@catalyst.net.nz \
--to=martin@catalyst.net.nz \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).