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

Re: [darcs-devel] Darcs and git: plan of action

From
JCJuliusz Chroboczek <juliusz.chroboczek@pps.jussieu.fr>
Date
Apr 20, 2005, 07:55 UTC
Message-ID
<7iy8bdswzz.fsf@lanthane.pps.jussieu.fr>
In-Reply-To
<20050419235832.56117.qmail@web51003.mail.yahoo.com>
> We're talking about interoperating with a Git repository here,
> right?  Even if we got the metadata in there, doesn't Git have to
> understand a replace patch for things to work out?
> 0. All three are in sync to begin with.
> 1. CC creates a token-replace patch, sends the changes in normal hunk
> format to AA.
> 2. BB makes changes, sends a normal hunk patch to AA and CC.  AA will
> apply the hunk normally.  For CC the token replace might apply here
> and so the result could be different.
3. when AA and CC try to sync, they will get spurious merge conflicts.
> Isn't this a potential problem?

It is. In a heterogeneous environment they will get spurious merge conflicts.

                                        Juliusz
Message 1 of 1 in “Re: [darcs-devel] Darcs and git: plan of action”
  1. Juliusz ChroboczekApr 20, 2005

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.