On Thu, Jun 27, 2013 at 3:41 PM, Woody Wu <narkewo...@gmail.com> wrote:
> On Thu, Jun 27, 2013 at 03:14:05PM +0200, Johan Herland wrote:
>> On Thu, Jun 27, 2013 at 2:46 PM, Woody Wu <narkewo...@gmail.com> wrote:
>> > 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?
>> If he can set up an SSH server on his machine (outside the company
>> network), then he can set up a mirror repo on his machine, where you
>> can push changes from the office to him, and pull changes from him
>> back into the office. Of course, you will probably need to synchronize
>> this with him, especially if he's travelling and frequently offline or
>> changing IP addresses. Also you need to be able to make outbound SSH
>> connections through the company firewall, but AFAICS that is usually
>> allowed.
> Outbound ssh to me is not a problem, but inbound ssh to him may be a big
> problem. You know hotel firewall or some home ADSL don't allow that.

In that case, you will need either:

A) A third machine, accessible from both you and him (preferably over
SSH), where you can store the repo. I don't know what your company
infrastructure looks like, but maybe it's possible to setup a server
in the DMZ outside your company firewall?

B) Use a more manual mechanism like emailing bundles (as explained by


Johan Herland, <jo...@herland.net>
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to