Stefan Reichör <[EMAIL PROTECTED]> writes: > Committed revision 517 to http://bzr.xsteve.at/dvc/ > > Implemented xgit-branch
In dvc-unified.el, you didn't use define-dvc-unified-command for dvc-*-branch. What is the rationale for this? The comment in dvc-unified.el for dvc-select-branch is not clear. What does "select" mean, in terms of what happens to the current workspace? The comment for dvc-create-branch doesn't say what the parent branch is. In xgit.el, xgit-branch takes an argument giving the new branch name, but dvc-create-branch takes no argument. Normally, we try to put all argument processing in the dvc front-end, so the user interface is more consistent across back-ends. Apparently the branch is created with the current branch of the current working directory as parent. In some cases, the user might want to specify a different parent branch. Do we want to require them to have that branch checked out? Does xgit-checkout change the branch of the current working directory? Does it preserve any uncommitted changes? How do I checkout a branch into a new working directory? xgit-branch-list takes an 'all' argument. What branches are left out if "all" is not specified? The 'all' option should be promoted to an argument to dvc-list-branches. mtn has a way to "suspend" a branch, so it no longer shows up in the branch list. The option --ignore-suspend-certs overrides that, so it would make sense to specify that option for "all". -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
