Matthieu Moy, 2007-04-10: > Christian Ohler <[EMAIL PROTECTED]> writes: > >>> -;; FIXME: I don't know what AGAINST is for. >>> +;; FIXME: use AGAINST >>> ;;;###autoload >>> -(defun xmtn-dvc-status (&optional against) >>> +(defun xmtn-dvc-status (&optional against path) >>> + "run monotone inventory on optional PATH (default current tree), display >>> results. >>> + >>> +AGAINST must be a revision specifier (number, last:N, >>> +revid:foobar, ...) or nil, but is currently not used." >> What's a "revision specifier"? It looks like a bzr thing. "number" and >> "last:N" don't make much sense for monotone. > > The examples seem to be taken from bzr. > > The idea is that you have different ways to identify a revision > (different, both in the sense "several, for a given back-end" and > "different, according to the back-end"). In bzr, last:3 means, "the > last but 3 revision in the current branch" for example. There are > several ways to identify the same revision.
Right, I'm familiar with revision _IDs_. Sorry if this wasn't clear from my message. The docstring refers to revision _specifiers_, though, which are a different beast, and bzr-specific. Next time I get around to posting a patch, I'll revert the documentation changes in this hunk because the docstring is appropriate only for bzr, not for xmtn. >> In what situations would it be useful to run dvc-status against a >> revision other than the workspace base revision? > > It depends on the back-end you use. > > For baz, for example (I don't care much about baz/tla right now, but > it has a strong historical influence on DVC), "status" mostly means > "short diff". So, you can compare you local tree with any other > revision. But does anyone actually use "status" like this? It seems to be what "diff" is for. Yes, diff is more detailed, but the dvc diff buffer will have a short summary at the top anyway. The usual model seems to be that "status" provides an overview of how the version control system sees the workspace, and what it's going to record when the user hits the commit button. In this model, computing the status against an arbitrary revision is meaningless. None of the backends except tla seem to implement the AGAINST argument; this also indicates that it can't be needed much. So, instead of having a note "not implemented in this backend" in every backend, let's just remove the argument. Christian. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
