-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark A. Flacy wrote:
| On 03/13/2008 03:19:53 PM, Sam Steingold wrote:
|> the current behavior leads to user errors when the said sad user has
|> to
|> switch between dvc and pcl-cvs frequently.
|> my suggestion that you elided
|>
|> -- by default, an operation in the *status* buffer applies to the file
|> ~   under cursor only, not the whole repository.
|> ~   this can be implemented as a user option
|> ~   dvc-status-no-selection-action which can have 3 values:
|> ~   == 'repository (current DVC behavior)
|> ~   == 'current-file (PCL-CVS behavior)
|> ~   == 'error (signal an error "no selection")
|>
|> permits the users to "play it safe" (when he has to switch often
|> between
|> dvc and pcl-cvs) and set it to 'error, while using the usual "whole
|> repo" conventions when he is not using cvs.
|> this will also simplify user transition from cvs to distributed VCs.
|
| Since there will be no reason to change your current behavior, I don't
| see how it will help with the transition.

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.

| Adding additional state to any program isn't free; there is the
| required code to implement the state in question, the additional test
| effort to ensure the code works, and the documentation effort to
| describe how that works. There's also the support effort to answer some
| user's question about why things aren't working in the expected fashion
| when someone else has modified a configuration to set this new variable
| to something other than the default.

As a maintainer of CLISP, I am well aware of this cost.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH3oe9Pp1Qsf2qnMcRAnF/AJ9D6/AezZRIVX+oZoShTBYckb1LYwCcC8Fq
WYuJBJuPMns7w/L3DM3HC+U=
=qJTl
-----END PGP SIGNATURE-----

_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev

Reply via email to