git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jakub Narebski <jnareb@gmail.com>
Date
Jan 22, 2008, 13:53 UTC
Message-ID
<m3k5m2klmh.fsf@roke.D-201>
In-Reply-To
<alpine.LSU.1.00.0801221255530.5731@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 27 quoted lines
> 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".

If I remember correctly either in GitFaq or GitTios at GitWIki (http://git.or.cz/gitwiki/), or in "Git in Nutshell" guide there is description how to generate incremental bundle containing all objects you created since last bundle and only those objects.

Besides, after initial setup IMHO it is much better to exchange patches for review. Although usually there are more than two developers in such case...

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Johannes SchindelinNext: Mark Levedahl
Message 3 of 9 in “Using email between 2 developers to keep git repositories in sync”
  1. ab_lists@mac.comJan 22, 2008
  2. Johannes SchindelinJan 22, 2008
  3. Jakub NarebskiJan 22, 2008
  4. Mark LevedahlJan 22, 2008
  5. ab_lists@mac.comJan 22, 2008
  6. Mark LevedahlJan 22, 2008
  7. Daniel BarkalowJan 22, 2008
  8. Annard BrouwerJan 22, 2008
  9. Theodore TsoJan 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.