-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel Dehennin wrote: | Le 5311 Septembre 1993, Sam Steingold a envoyé: |> setting dvc-status-no-selection-action to 'error makes the user |> eminently aware of the differences between dvc & pcl-cvs and makes him |> change his behavior to specify _strictly_ what files he wants to operate on. |> |> an alternative is to learn from "hg revert" which refuses to operate on |> the whole repo unless --all is specified in a start contrast with "hg |> commit" which does not require --all to operate on the whole repository. |> specifically, when there is no selection, dvc should ask for |> confirmation before operating on the whole repository. |> this, of course, could be implemented by the 'confirm value of |> dvc-status-no-selection-action. | | As a DVC user, I think that it should be backend-dependent. | I think DVC should mimic the backend on such points.
OUCH - NO! these "modern distributed VC systems" are proliferating like rats in a garbage dump, each having its own precious set of commands and conventions. bzr, hg, git - each is different. when I have to use hg for work, git for gnulib and bzr for emacs, I want a uniform interface which DTRT for each underlying backend. dvc has a chance of creating a de-facto interface standard which all these backends will have to be able to mimic to be supported by dvc. go for it! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH3qg0Pp1Qsf2qnMcRArykAJ9f2Fpou+NW6lFnvorNdkex/+O5bgCfVhwv R4Fg0QNYQa6wy4n2CAoSddw= =iZmc -----END PGP SIGNATURE----- _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
