From: Avery Pennarun <apenwarr@gmail.com>
To: Sultan Shakir <sshakirflhosp@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Can Git work for us if we are remotely hosted?
Date: Thu, 12 Aug 2010 14:29:56 -0400 [thread overview]
Message-ID: <AANLkTinv1qt+vXH0gMpxBKsm-u9EGL2LEWVrRQDyrqhr@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=wa_xdheoKDPr=rfugttpu56s-sd3Q6qFgBALL@mail.gmail.com>
On Thu, Aug 12, 2010 at 2:22 PM, Sultan Shakir <sshakirflhosp@gmail.com> wrote:
> On Thu, Aug 12, 2010 at 2:08 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
>> You said you have "access to the backend where the files are stored."
>> Surely that's on a fileserver, like a Windows file sharing service or
>> a samba server or an NFS server, right? Any of those are capable of
>> holding a git repository.
>>
>> git is much faster if you store files on your local machine as much as
>> possible. But you can push/pull from a shared repository on a
>> samba/NFS/whatever server and that generally won't be a performance
>> problem.
>
> Thanks Avery. Wouldn't this defeat the purpose of using Git since we
> can't really run nor can we compile files on our local machines?
I don't know; you didn't say what was your purpose for using git.
You can run git directly with files on a network drive, but it'll be
much slower than it should be. You might argue that *that* defeats
the purpose of using git too, since of the best features of git is how
fast it is :)
Have fun,
Avery
prev parent reply other threads:[~2010-08-12 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 22:51 Can Git work for us if we are remotely hosted? Sultan Shakir
2010-08-11 23:06 ` Avery Pennarun
2010-08-12 17:59 ` Sultan Shakir
2010-08-12 18:08 ` Avery Pennarun
2010-08-12 18:22 ` Sultan Shakir
2010-08-12 18:29 ` Avery Pennarun [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=AANLkTinv1qt+vXH0gMpxBKsm-u9EGL2LEWVrRQDyrqhr@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=sshakirflhosp@gmail.com \
/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).