From: Sultan Shakir <sshakirflhosp@gmail.com>
To: git <git@vger.kernel.org>
Subject: Can Git work for us if we are remotely hosted?
Date: Wed, 11 Aug 2010 18:51:14 -0400 [thread overview]
Message-ID: <AANLkTin4JyZhmjm_1c4q7kjP0eXzA-_2eNsLzsnGASet@mail.gmail.com> (raw)
I've been trying to wrap my brain around how I can get Git to work at
my organization. The issue is that nearly all of our programs and
their IDE are remotely hosted. This means that to even work on a file
we have to connect to the network in order to use the application that
we code in. We do have access to the backend where the files are
stored though. How can we use Git in this situation without setting
up another server?
next reply other threads:[~2010-08-11 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 22:51 Sultan Shakir [this message]
2010-08-11 23:06 ` Can Git work for us if we are remotely hosted? 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
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=AANLkTin4JyZhmjm_1c4q7kjP0eXzA-_2eNsLzsnGASet@mail.gmail.com \
--to=sshakirflhosp@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 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).