Erik, On 31 March 2014 23:12, Erik Carstensen <[email protected]> wrote: > Here is an implementation of stg move.
Is there a way to decompile a .pyc file? It's easier if you sent the .py one directly ;). > 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). I think that's fine, Karl know more about this. > - 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. So we won't have default options. Fine by me. > - The patch log is not copied to the new branch. I never used patch logs, so > I don't know about your expectations there. I don't use them much either. It can be added afterwards if we find a way. > - 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 is make_patch_name() in stgit/utils.py. See __create_patch() in stgit/commands/imprt.py for an example on how to use this. Catalin _______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
