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

stgit: another way of storing patches

From
Jon Smirl <jonsmirl@gmail.com>
Date
Nov 20, 2007, 14:53 UTC
Message-ID
<9e4733910711200653g4d87c433gae2d48f3508940f5@mail.gmail.com>

What about storing each stg git patch in a branch and then auto-merging them into the working copy? That would allow per patch history and undo. Would it make them easier to share? You could use tag names to tell stg how to merge and make the working branch.

-- 
Jon Smirl
jonsmirl@gmail.com
Next: Karl Hasselström
Message 1 of 2 in “stgit: another way of storing patches”
  1. Jon SmirlNov 20, 2007
  2. Karl HasselströmNov 21, 2007

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.