On 20 December 2011 09:45, Marc Herbert <[email protected]> wrote: >>> Couldn't a new stg patch name be sneaked into some "private"/reserved >>> git metadata field? >> >> I'm not sure. We could add some field in the message as well but I was >> looking for easy interworking with standard "git rebase". Once you >> touch the stack outside StGit, it gets confused because commit ids no >> longer match the patches. > > Is "git notes" the answer? > > http://progit.org/2010/08/25/notes.html
I don't think it helps much since 'git rebase' doesn't generate notes for the new commits. The notes are still attached to the old commit. It needs something that is generated by 'git format-patch' and re-imported by 'git am' (that's how 'git rebase' works). We could always place some information in the patch description but it's not always nice. -- Catalin _______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
