From: Johannes Sixt <j.sixt@viscovery.net>
To: Felipe Carvalho Oliveira <felipekde@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
git@vger.kernel.org
Subject: Re: Tip: avoiding net overhead using git over sshfs
Date: Thu, 23 Oct 2008 14:54:16 +0200 [thread overview]
Message-ID: <490073F8.6080509@viscovery.net> (raw)
In-Reply-To: <a2075f4c0810230451lefff6ffnc283f4078eff9f9c@mail.gmail.com>
Felipe Carvalho Oliveira schrieb:
> On Thu, Oct 23, 2008 at 7:00 AM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
>> I think you'd better work locally, and push to the sshfs directory
>> from time to time. Then, you'd both have working tree and .git locally
>> and fast, while keeping the safety of replicating to your ssh server.
>
> I can't use git-push as I explained before.
> I use git as a deployment tool in this case.
> I work locallly and use git-pull to sync my local repo and the
> "production"(server).
> Git works better than a manual (S)FTP sync.
Then how about this: You keep your repository local, and you also hack
locally. When it's time to push your changes to the production server, you
do this:
$ GIT_INDEX_FILE=.git/index.published \
GIT_WORK_TREE=/sshfs-mount/on/production/server \
git reset --hard
This will update only files that changed since you did this the last time.
Disclaimer: I didn't try this myself.
-- Hannes
next prev parent reply other threads:[~2008-10-23 12:55 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
2008-10-23 11:51 ` Felipe Carvalho Oliveira
2008-10-23 12:54 ` Johannes Sixt [this message]
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=490073F8.6080509@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Matthieu.Moy@imag.fr \
--cc=felipekde@gmail.com \
--cc=git@drmicha.warpmail.net \
--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.