Hi Stephen! > I'm starting to use git, so I'm starting to use the dvc front end to > git. > > I'm used to the dvc front end to mtn, which has some higher-level > functionality. > > In particular, xmtn-status-one creates a buffer that lists the > operations that are needed to bring a workspace in sync with the local > repository; commit, resolve conflicts, merge, or update. > > In addition, xmtn-status-multiple gives the same info for all > workspaces > under a common root directory; very handy for related workspaces. > > I'd like to have that for git as well, so I'm converting that code to > be > back-end agnostic. > > It needs a better name, since dvc-status is already taken. I'm > tentatively using 'dvc-state'. > > There's already a 'dvc-state.el'; it provides persistence, so I'm > renaming it to 'dvc-persistence.el', although not changing the function > names. > > Suggestions?
That is really good news that you are going to improve the git backend. Your plan sounds good to me! Stefan. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
