stgit: another way of storing patches

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.

On 2007-11-20 09:53:55 -0500, Jon Smirl wrote:

You mean making a "patch" be a topic branch rather than just one commit, with the successive commits on the topic branch reflecting the changes to the patch over time?

How would you handle operations such as refreshing a non-topmost patch, reordering patches, dropping patches, etc? It seems to me that the operation you'd want then would look more like cherry-picking than merging, at least sometimes.

It might work, but someone would have to sit down with pen and paper and work out how all the common operations should work.