Stephen Leake <[EMAIL PROTECTED]> writes: > Stefan Reichör <[EMAIL PROTECTED]> writes: > >> Stephen Leake <[EMAIL PROTECTED]> writes: >> >>> 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? >> >> I am not sure, if we can use the same parameter list for all backends. >> dvc-* commands are normally not used for elisp scripting. They are used >> to invoke a command and DVC ensures that the correct backend is >> involved. >> >> The way I implemented it now, allows to have different parameters for >> each backend. I didn't look at other backends in detail, so I don't know >> if this is really needed. > > I believe the convention is that at the top level > <backend>-dvc-<function>, the command list is the same. Backends can > extend that with &optional if they want to. >> >>> 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? >> >> In git select just switches to a different view (called branch) in the >> current directory. > > I still don't know what that means. > > Does only metadata change? is the new branch checked out? What files > are affected?
Why not try it? Use the git command line or stefan's new functions. All files change that are different in the new branch as far as I can see. Which makes sense.It's a branch. It would be pretty useless if you changed branch and did not get that new branches files. Its also why you can not switch to another branch with uncommited changes I think. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
