All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: git over rsync+ssh
Date: Thu, 10 Jul 2008 12:09:14 +0200	[thread overview]
Message-ID: <g54n4a$kek$2@ger.gmane.org> (raw)
In-Reply-To: <20080709171721.GA3679@mithlond.arda.local>

Teemu Likonen venit, vidit, dixit 09.07.2008 19:17:
> Avery Pennarun wrote (2008-07-09 12:02 -0400):
> 
>> I don't know if this will help in your case, but if it will be only
>> you pushing to this repository, one option is to simply create a bare
>> push repository on your local machine, and then manually just
>> rsync+ssh it to the remote machine from the command line as
>> a so-called "push" operation.
> 
> Again, I don't know if this is helpful for Michael, but this "manual"
> rsyncing can be done automatically via hooks/post-receive. Just like
> Avery said, "git push" to a bare repository in a local machine and this
> bare repo has post-receive hook which does "git update-server-info" and
> the rsyncing (or "sitecopy --update" or similar).

Thanks for your hints. Your posts combined made me understand the trick, 
using the "auxiliary" local repo for the hooks triggering the rsync. 
I'll hopefully remember it when I need it; in this case, a second repo 
would not have been very convenient, but I managed to get git running on 
the server side meanwhile.

Michael

  reply	other threads:[~2008-07-10 10:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 14:01 git over rsync+ssh Michael J Gruber
2008-07-09 15:02 ` Mike Ralphson
2008-07-10 10:06   ` Michael J Gruber
2008-07-09 16:02 ` Avery Pennarun
2008-07-09 17:17   ` Teemu Likonen
2008-07-10 10:09     ` Michael J Gruber [this message]
2008-07-09 20:33 ` Stephen Sinclair
2008-07-10 10:14   ` Michael J Gruber

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='g54n4a$kek$2@ger.gmane.org' \
    --to=michaeljgruber+gmane@fastmail.fm \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.