Richard Riley <[EMAIL PROTECTED]> writes: > Not having the branch commands in DVC for git would immediately > invalidate its usage for a lot of people I think.
That may be true, but I hope not. Every GUI interface to a CM system I've used requires occasional command line use. For some operations (like renaming lots of files), the command line is better. I use the commannd line for branching in mtn; there is no xmtn-branch command in DVC. In fact, I wrote a customized mtn command for branching, because I have four related projects that should be branched together for my simulators (named GDS); makerules (a collection of core make files), sal (a low-level library for spacecraft math), common (the core shared code for the simulator), lro (the Lunar Reconnaisance Orbiter mission-specific simulator code). there are also other missions. mtn commands can be written in Lua, and invoke other mtn commands. In this case, it was easier to do that, and the resultant command runs faster, than doing the equivalent in elisp for a custom xmtn-gds-branch command. That said, there may be a reasonable way to implement a dvc-branch command. What would you like it to do? > branching and staging are two of the most used features of git in my > (limited) experience. Once you get going, commit and merge will be more common; you should not have to create branches often. -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
