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
Mark Levedahl <mlevedahl@gmail.com>
Date
Jan 22, 2008, 16:00 UTC
Message-ID
<30e4a070801220800l6f38bbe5wc6b1ceeac7efbf06@mail.gmail.com>
In-Reply-To
<4F8D70B2-B264-46FF-BFBB-01AEF42DD888@mac.com>
On Jan 22, 2008 10:05 AM,  <ab_lists@mac.com> wrote:
Show 6 quoted lines
> Thank you all for your feedback!
>
> So would it be wise to synchronise the repositories over time using
> the bundles and despite having exchanged email patches or should they
> be used separately?
>

You can use both: patches to distribute proposed changes, bundles to distribute the integrated (and presumably controlled) branches after changes are accepted. Of course, you can use a bundle to distribute a proposed change as well (as a topic branch), you have to decide for yourselves what works best. Patches are great for distributed review over a mailing list, but if only a couple of you and no mailing list that advantage diminishes.

Mark
Previous: ab_lists@mac.comNext: Daniel Barkalow
Message 6 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.