Hi, Here is an implementation of stg move.
I tried to only use the "new infrastructure" (i.e., I avoided all library functions that weren't written in Karl's coding style). Some notes: - I didn't use a transaction for creating patches in the new branch, because patch creation cannot fail (and transactions don't span multiple branches). - Branches are given with explicit options --from and --to. Specifying none would be a strange way of expressing pop, and likely a mistake, so I made that an error. - The patch log is not copied to the new branch. I never used patch logs, so I don't know about your expectations there. - Is there a function to pick a name for a patch? I couldn't find one, so I rewrote the logic instead (find_unique_name). It would be better to use an existing one, or to promote mine to a library if none exists. - There are no tests yet On Fri, Mar 28, 2014 at 3:44 PM, Karl Wiberg <[email protected]> wrote: > On Fri, Mar 28, 2014 at 5:07 AM, David Kågedal <[email protected]> wrote: > > No, it's not a delete operation. > > I agree---at this level, generally name things after user intent, > since the user isn't expected to know anything about the > implementation. > > -- > Karl Wiberg, [email protected] > subrabbit.wordpress.com > www.treskal.com/kalle >
move.pyc
Description: application/python-bytecode
_______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
