Re: Using email between 2 developers to keep git repositories in sync

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 22, 2008, 13:00 UTC
Message-ID: <alpine.LSU.1.00.0801221255530.5731@racer.site>
In-Reply-To: <7A02F7D1-9EB0-43AB-96F9-DDD71D4EF5FE@mac.com>

Hi,

On Tue, 22 Jan 2008, ab_lists@mac.com wrote:

> However I need to share code with a co-developer. He also has a code 
> base that I need access to. For several reasons, a shared server will 
> not work so I was thinking of using email to send patches back and 
> forth.

My recommendation: Use bundles.  Just make the initial "clone" like this:

	$ git bundle create initial.bundle --all

Send the file "initial.bundle" (which you just created) to your co-developer. He should now initialise his repository:

	$ mkdir my-new-workdir
	$ cd my-new-workdir
	$ git init
	$ git pull /path/to/initial.bundle master

(Someone tried to get "git clone /path/to/bundle" to work, but I don't know if that work was ever completed, so I assume it was not.)

Whenever he wants to send you an update, he has to do something like this:

	$ git bundle create update.bundle --all --since=2.weeks.ago

and send you the resulting file named "update.bundle".

Hth, Dscho