[Cc: git@xxxxxxxxxxxxxxx] Catalin Marinas wrote: > BTW, if it's not clear for me how to initially structure a patch > series, I add everything to a patch and create underlying patches > afterwards and pick hunks from the big one (usually manually, though > native support in StGIT for this would be good, as someone pointed out > on this list). If all the hunks in the big patch were added to other > patches, pushing the big one should result in an empty patch > automatically (because of the three-way merging) and can be safely > removed. Perhaps this calls for "stg duplicate" command, which would result in duplicating patch (perhaps one would need to provide name for the first patch, and optionally laso for second patch) in such way that first copy would be on top of aplied stack, and second copy (the duplicate, with an old name) would be at the bottom of the deck of unapplied patches. This way if you want to for example split patch into two, you would do $ stg duplicate new-name $ edit files $ stg refresh $ stg push And similarly (with more duplicates) if you want to split it more. What do you think about this? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html