This is something that I want to do frequently as well, and I think your suggestion makes sense. But I haven't thought very hard about it.
2014-03-19 17:13 GMT+01:00 Erik Carstensen <[email protected]>: > Hi, > > Sometimes when I'm working on a topic branch, I happen to fix a problem > that is quite unrelated to the topic of the branch. E.g., it could be that > I fix a spelling error in the documentation of some utility function. > > What usually happens is that I commit the change to 'topic', because > that's what I have checked out, and then at a later point I try to move the > patch to 'master'. I find this process a bit cumbersome: > git checkout master > stg pick -B topic fix-spelling > git checkout topic > stg delete fix-spelling > > To me it would be nice if this could be streamlined. In particular, I > would like to avoid switching between branches (because it forces a > rebuild, and because it cannot be done while I have a dirty working tree). > > I can understand that it's not possible to push a patch onto a branch > unless that branch is checked out (because of potential merge conflicts). > What I'm looking for is a way to move a patch to another branch without > actually applying it; i.e., the equivalent of 'stg pick --unapplied' but > onto a different stgit branch. > > Is it possible to do this already? If not, is it a reasonable feature > request? > > Erik > > _______________________________________________ > stgit-users mailing list > [email protected] > https://mail.gna.org/listinfo/stgit-users > > -- David Kågedal
_______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
