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
ABAnnard Brouwer <ab_lists@mac.com>
Date
Jan 22, 2008, 22:52 UTC
Message-ID
<2D91636D-197A-41C8-8BB3-D5002135BF99@mac.com>
In-Reply-To
<alpine.LNX.1.00.0801221713120.13593@iabervon.org>

Thank you all for your suggestions! The problem is that each of us having a local server accessible to the other is not possible. Therefore I will follow the path of sending patches by email and on releases we can synchronise using bundles. I think that's the best fit for our model of developing code semi-independently.

Cheers! Annard

On 22 Jan 2008, at 23:22, Daniel Barkalow wrote:
Show 10 quoted lines
> I think bundles or email or both is likely to be the correct  
> solution, but
> you should know that you don't need a shared server if you each have a
> server the other can read from. Each of you sets up a public  
> repository
> with the same basic history, and you each have local clones of your  
> public
> repository, and you pull from the other into your local clone and
> (assuming you want to accept the other's changes) you do the merge and
> push to your own public server.
Previous: Daniel BarkalowNext: Theodore Tso
Message 8 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.