git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Woody Wu <narkewoody@gmail.com>
To: git <git@vger.kernel.org>
Subject: Off-line deverloper workflow?
Date: Thu, 27 Jun 2013 20:46:56 +0800	[thread overview]
Message-ID: <20130627124656.GA2620@zuhnb712> (raw)

Hi,

I have a colleague who has to left our office for three month, but still
need to work on the project which is hosted on our in-office git
repository. Problem is that our company has firewall, it's not possible
or not allowed to access the company LAN outside the building.  So I
want to ask you expert, can you suggest a best practice of git workflow
that suitable to my situation?

Thanks in advance.

-woody

             reply	other threads:[~2013-06-27 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 12:46 Woody Wu [this message]
2013-06-27 12:58 ` Off-line deverloper workflow? Fredrik Gustafsson
2013-06-27 13:06 ` Tim Chase
2013-06-27 13:37   ` Woody Wu
2013-06-27 13:14 ` Johan Herland
2013-06-27 13:41   ` Woody Wu
2013-06-27 13:47     ` Johan Herland
2013-06-27 13:43 ` Jean-Noël Avila
2013-06-27 13:58   ` Woody Wu
2013-06-27 17:17   ` Junio C Hamano

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=20130627124656.GA2620@zuhnb712 \
    --to=narkewoody@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).