git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Elfyn McBratney <beu@gentoo.org>,
	git@vger.kernel.org, Martin Langhoff <martin@catalyst.net.nz>
Subject: Re: [PATCH] Cogito README: add a block describing team workflow with git+ssh
Date: Fri, 30 Sep 2005 09:52:11 +1200	[thread overview]
Message-ID: <46a038f905092914524d3cd8c1@mail.gmail.com> (raw)
In-Reply-To: <20050929212511.GA28106@zippy.emcb.local>

On 9/30/05, Elfyn McBratney <beu@gentoo.org> wrote:
> > +        $ chgroup gitcommit /var/git
>
> s/chgroup/chgrp/

Ooops! Thanks for catching that

> > +        $ chmod  2775 /var/git
> > +        $ mkdir -p /var/git/projectname.git
> > +        $ GIT_DIR=/var/git/projectname.git git-init-db
>
> Hmm .. if you're you're going to be using cogito anyway, might it be an
> idea to instead do:
>
>         $ GIT_DIR=/var/git/projectname.git/.git cg-init [-I]

You only really need git on the repo server, and I think that's a plus.

> > +        $ git-push  remoteserver:/var/git/projectname.git master branchname
>
> Ditto here, tho' that'll require that remotes have been set-up, of
> course. ;)

Yes, the cogito way of doing this seems messy. Is there a simple way
to set up the remote branch and push to it?

cheers,


martin

  reply	other threads:[~2005-09-29 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  6:31 [PATCH] Cogito README: add a block describing team workflow with git+ssh Martin Langhoff
2005-09-29 21:25 ` Elfyn McBratney
2005-09-29 21:52   ` Martin Langhoff [this message]
2005-09-29 22:19     ` Elfyn McBratney
  -- strict thread matches above, loose matches on Subject: below --
2005-10-21  5:34 Martin Langhoff
2005-10-21 15:14 ` Petr Baudis

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=46a038f905092914524d3cd8c1@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=beu@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=martin@catalyst.net.nz \
    /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).