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

Using email between 2 developers to keep git repositories in sync

From
Aab_lists@mac.com <ab_lists@mac.com>
Date
Jan 22, 2008, 12:47 UTC
Message-ID
<7A02F7D1-9EB0-43AB-96F9-DDD71D4EF5FE@mac.com>
Hello there,

I have been converted to git after reading good things about it. I have been using it with a personal project and so I'm familiar with the basics. 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 question is related to the initial setup and sharing of our repositories. Would it be necessary for each of us to make a clone and make a tarball of that clone to send to one another before we can send patches? The documentation is all based on using a git or ssh server to set this up.

Thank you for any insights you can provide me! Annard

Next: Johannes Schindelin
Message 1 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.