{"thread":{"id":"21759","subject":"[StGit] push/pull stacked patches","startedAt":"2009-11-26T12:17:38Z","lastAt":"2009-11-26T12:17:38Z","messageCount":1,"participants":["Kurt Harriman"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"128456","messageId":"4B0E71E2.3040908@acm.org","threadId":"21759","inReplyTo":null,"subject":"[StGit] push/pull stacked patches","fromName":"Kurt Harriman","fromEmail":"harriman@acm.org","sentAt":"2009-11-26T12:17:38Z","receivedAt":"2009-11-26T12:17:38Z","isPatch":false,"sender":{"key":"harriman@acm.org","avatar":null},"body":"Suppose two developers are collaborating on a series of patches.\nWhat is the best way to synchronize their repositories, including\nthe StGit state?\n\nEven if both repositories are StGit-enabled, the patch metadata\nand unapplied patches don't seem to be transferred by push/pull.\n\nApplied patches are transferred as ordinary commits, losing\ntheir patch names and their place in the patch stack.\nIt seems that a remote branch cannot have a patch stack.\n\nInstead of using push/pull, a patch series can be transferred\nusing stg export/import, but this is error-prone, requiring\nextra steps, and changes the commit timestamp and SHA1.\nStg export/import are good for distributing the final version\nof a patch series; but ungitly for back-and-forth collaboration.\nIs there a better way?\n"}]}