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

Re: Clarifications for merge workflows

From
MEMarkus Elfring <markus.elfring@web.de>
Date
Mar 11, 2010, 13:02 UTC
Message-ID
<4B98E9CC.9000700@web.de>
In-Reply-To
<7v63532h82.fsf@alter.siamese.dyndns.org>
Thanks for your explanation.
> And then the procedure to publish the result out, whether it is what I did
> myself, or what I helped to integrate into my history from others, is the
> same.  I push the result out from that "local" place to the "public" one.

Does any observable difference exist if the data synchronisation would be performed in the other direction?

> Of course, if you are always working on that "server", the fact that you
> are always working there makes it the most convenient place to do all of
> your work for you.

I guess that it matters a bit if the published repository "SHARE" is the leading and authoritative storage location.

Regards, Markus

Previous: Junio C Hamano
Message 3 of 3 in “Clarifications for merge workflows”
  1. Markus ElfringMar 11, 2010
  2. Junio C HamanoMar 11, 2010
  3. Markus ElfringMar 11, 2010

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.