From: Martin Langhoff <martin.langhoff@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Really happy with cogito for inhouse teamwork, now that I've figured out cg-clone...
Date: Thu, 29 Sep 2005 17:58:56 +1200 [thread overview]
Message-ID: <46a038f905092822587f5414d4@mail.gmail.com> (raw)
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
next reply other threads:[~2005-09-29 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 5:58 Martin Langhoff [this message]
2005-09-29 15:15 ` Really happy with cogito for inhouse teamwork, now that I've figured out cg-clone Josef Weidendorfer
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=46a038f905092822587f5414d4@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--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