From: "Jean-Noël Avila" <avila.jn@gmail.com>
To: Woody Wu <narkewoody@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Off-line deverloper workflow?
Date: Thu, 27 Jun 2013 15:43:51 +0200 [thread overview]
Message-ID: <51CC4197.3000007@gmail.com> (raw)
In-Reply-To: <20130627124656.GA2620@zuhnb712>
Le 27/06/2013 14:46, Woody Wu a écrit :
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
For a short time, I had the same issue. We came up using "git bundle" to
bundle changes and exchange them via email.
The setup was to work in two separate branches. The roaming developper
started a new branch when leaving. After some work, she sent the commits
on her branch as a bundle file. The origin merged the branch extracted
from the developper's bundle and sent back the bundle of the changes on
origin since the last merge.
No doubt that both side need to understand well the workflow of
fetch/merge. Bundle files can be encrypted for better security.
Hope this helps.
JN
next prev parent reply other threads:[~2013-06-27 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 12:46 Off-line deverloper workflow? Woody Wu
2013-06-27 12:58 ` 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 [this message]
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=51CC4197.3000007@gmail.com \
--to=avila.jn@gmail.com \
--cc=git@vger.kernel.org \
--cc=narkewoody@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).