Right! There seems to be a consensus now. I'll try to implement a command stg move PATCH BRANCH with no additional args, which: - pops PATCH, rolling back the change on conflicts - adds it unapplied to BRANCH - removes it from BRANCH
We can consider adding flags -b and --push later, if there is a need for it. On Wed, Mar 26, 2014 at 5:30 PM, Catalin Marinas <[email protected]>wrote: > On 26 March 2014 15:08, Karl Wiberg <[email protected]> wrote: > > On Wed, Mar 26, 2014 at 4:54 AM, Erik Carstensen <[email protected]> > wrote: > >> synopsis: > >> stg move PATCH BRANCH > >> moves PATCH to remote branch BRANCH > >> -b BRANCH: move from BRANCH instead of current branch (will not be > >> implemented initially) > >> --unapplied: keep patch unapplied in remote branch > > > > Seems much better. Personally, I'd change the default and have --push > > instead of --unapplied, though; pushing seems to me to conceptually be > > a separate step on top of moving from one branch to another. > > Unapplied by default seems better to me as well. > > >> I think I like (c) best, because it does what you probably > >> wanted. (a) is OK too, if the message can hint about --unapplied. I > >> don't like (b), because it makes me lose the stack top. > > > > That makes sense to me. > > I agree. > > BTW, if Erik is implementing this, just use the stgit.lib classes > similar to 'push' rather than based on 'pick'. > > Thanks. > > -- > Catalin >
_______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
