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

Re: Dividing up a large merge.

From
Avery Pennarun <apenwarr@gmail.com>
Date
Jul 15, 2009, 00:34 UTC
Message-ID
<32541b130907141734o59d224i7e0f39aa8a85e8ef@mail.gmail.com>
In-Reply-To
<20090715002926.GA26630@huya.quicinc.com>
On Tue, Jul 14, 2009 at 8:29 PM, <davidb@quicinc.com> wrote:
> The real issue is that there isn't any single individual who
> understands all of the code that conflicts.  It has to be divided
> up somehow, I'm just trying to figure out a better way of doing
> it.

How about having one person do the merge, then commit it (including conflict markers), then have other people just make a series of commits removing the conflict markers?

Avery
Previous: davidb@quicinc.comNext: davidb@quicinc.com
Message 4 of 13 in “Dividing up a large merge.”
  1. davidb@quicinc.comJul 14, 2009
  2. Bryan DonlanJul 15, 2009
  3. davidb@quicinc.comJul 15, 2009
  4. Avery PennarunJul 15, 2009
  5. davidb@quicinc.comJul 15, 2009
  6. Douglas CamposJul 15, 2009
  7. Avery PennarunJul 15, 2009
  8. Theodore TsoJul 15, 2009
  9. Jakub NarebskiJul 15, 2009
  10. Theodore TsoJul 15, 2009
  11. Larry D'AnnaJul 15, 2009
  12. Daniel BarkalowJul 15, 2009
  13. davidb@quicinc.comJul 15, 2009

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.