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

Re: Dividing up a large merge.

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 15, 2009, 13:39 UTC
Message-ID
<m31voiuktb.fsf@localhost.localdomain>
In-Reply-To
<20090715122828.GA6570@mit.edu>
Theodore Tso <tytso@mit.edu> writes:
> Yeah, that's another prime argument for maintaining your changes as a
> patch queue.  I use a combination of quilt plus git.
Why not StGit, or Guilt, or TopGit?
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Theodore TsoNext: Theodore Tso
Message 9 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.