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:14:43 +0200 [thread overview]
Message-ID: <g54nek$mbe$1@ger.gmane.org> (raw)
In-Reply-To: <9b3e2dc20807091333l38260b88na89939bdde09508e@mail.gmail.com>
Stephen Sinclair venit, vidit, dixit 09.07.2008 22:33:
> On Wed, Jul 9, 2008 at 10:01 AM, Michael J Gruber
> <michaeljgruber+gmane@fastmail.fm> wrote:
>> I want to put a git repo on a server where I have ssh access but failed to
>> compile git (AIX 5.1, has libz.a but no .so nor headers; compiling
>> prerequisite zlib failed, probably due to a botched build environment).
>>
>> As far as I can see my only option for a private repo is using rsync over
>> ssh.
>
> Have you tried sshfs?
Yes, in other cases, with mixed success. In the present situation, I'm
just John Doh User on both the client and the server, no sshfs available.
> It allows you to mount an ssh-accessible file system onto your local
> file system.
> This might make it possible to use your local git to access the remote account.
> Not sure of the implications for data integrity...
Integrity would be okay (single developper). But git is fast with a fast
filesystem, not so fast on NFS; on sshfs? I'm not even sure sshfs is
"filesystem-like" enough for git. Have you tried it with git?
Michael
P.S.: Problem solved differently now: got git going(TM) on the server.
prev parent reply other threads:[~2008-07-10 10:16 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
2008-07-09 20:33 ` Stephen Sinclair
2008-07-10 10:14 ` Michael J Gruber [this message]
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='g54nek$mbe$1@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 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).