From: Michael J Gruber <git@drmicha.warpmail.net>
To: Felipe Carvalho Oliveira <felipekde@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Tip: avoiding net overhead using git over sshfs
Date: Thu, 23 Oct 2008 10:32:34 +0200 [thread overview]
Message-ID: <490036A2.20608@drmicha.warpmail.net> (raw)
In-Reply-To: <a2075f4c0810221826w511a3b87r6fea4fb0dee24e1f@mail.gmail.com>
Felipe Carvalho Oliveira venit, vidit, dixit 23.10.2008 03:26:
> Use git over sshfs is not so good, but is an option for people that
> don't have shell acess to the server/hosting like me.
I'm sorry but I'm afraid I'm missing the point: If you don't have shell
access then you can't use ssh(fs), can you?
Maybe you mean you can't set up git daemon or gitweb.cgi on the server?
> # mounting
> sshfs -o workaround=rename <user>@<host>:/home/<user>/ <mount_point>
> cd <the_directory_of_your_project>
>
> # we will move the .git directory to the local filesystem
> mv .git ~/.my_project_git
> # and create a symlink to the local .git
> ln -s ~/.my_project_git .git
>
> Done!
>
> Now you can open gitk instantly ;-) and don't need to have the entire
> .git thing on a remote filesystem.
In fact your complete git repository is now on the local filesystem,
with only the worktree checked out on sshfs. Is that what you are trying
to achieve? Or do you want to "synchronize" repos on local and sshfs
filesystems?
Michael
next prev parent reply other threads:[~2008-10-23 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 1:26 Tip: avoiding net overhead using git over sshfs Felipe Carvalho Oliveira
2008-10-23 8:32 ` Michael J Gruber [this message]
2008-10-23 11:51 ` Felipe Carvalho Oliveira
2008-10-23 12:54 ` Johannes Sixt
2008-10-23 9:00 ` Matthieu Moy
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=490036A2.20608@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=felipekde@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 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.