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

[StGit] push/pull stacked patches

From
KHKurt Harriman <harriman@acm.org>
Date
Nov 26, 2009, 12:17 UTC
Message-ID
<4B0E71E2.3040908@acm.org>

Suppose two developers are collaborating on a series of patches. What is the best way to synchronize their repositories, including the StGit state?

Even if both repositories are StGit-enabled, the patch metadata and unapplied patches don't seem to be transferred by push/pull.

Applied patches are transferred as ordinary commits, losing their patch names and their place in the patch stack. It seems that a remote branch cannot have a patch stack.

Instead of using push/pull, a patch series can be transferred using stg export/import, but this is error-prone, requiring extra steps, and changes the commit timestamp and SHA1. Stg export/import are good for distributing the final version of a patch series; but ungitly for back-and-forth collaboration. Is there a better way?

Message 1 of 1 in “[StGit] push/pull stacked patches”
  1. Kurt HarrimanNov 26, 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.