From: Woody Wu <narkewoody@gmail.com>
To: Tim Chase <git@tim.thechases.com>
Cc: Woody Wu <narkewoody@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Off-line deverloper workflow?
Date: Thu, 27 Jun 2013 21:37:32 +0800 [thread overview]
Message-ID: <20130627133732.GA5047@zuhnb712> (raw)
In-Reply-To: <20130627080605.067af4ae@bigbox.christie.dr>
On Thu, Jun 27, 2013 at 08:06:05AM -0500, Tim Chase wrote:
> On 2013-06-27 20:46, Woody Wu 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?
>
> It would help to know a little more about the information flow and
> the starting conditions.
>
> - Was a clone of code made before leaving your office or does your
> colleague need to obtain the initial copy too?
Yes, he had a clone already.
>
> - How securely do you need to transfer matters? (email? shared
> external service like Dropbox/Box.com/etc)
I prefer email.
>
> - How frequently do updates need to be made?
>
Maybe once several days.
> - In which direction do commits flow? Just from your colleague back
> to the office, or are there other updates happening in the office
> that your colleague needs to pull down to keep in sync?
Bi-direction, means my colleague and my in-house team need to modify the
code.
>
> Without such answers, it's a little hard to suggest more than
> transmitting either patch files or bundles using any of the following:
> email, a shared cloud drive, a shared host out accessible on the net,
> or sneakernet media (flash-drive or CD/DVD, perhaps via the postal
> system), or possibly other means.
>
> You may want to read more at
>
> git help format-patch
> git help am
> git help bundle
>
> -tkc
>
>
>
>
--
I can't go back to yesterday - because I was a different person then
next prev parent reply other threads:[~2013-06-27 13:37 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 [this message]
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=20130627133732.GA5047@zuhnb712 \
--to=narkewoody@gmail.com \
--cc=git@tim.thechases.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).