Matthieu Moy <[EMAIL PROTECTED]> writes:

>> I think the git index/montone workspace manifest fit in category 1);
>> they extend the information that can be displayed in the status
>> buffer. In fact, that is mostly what motivated my rewrite of the
>> status ewoc; the old one did not allow displaying all of the
>> information. I just didn't know enough to say so clearly at the time
>> :)
>
> It's not just about the information displayed. In git, for example,
> git-diff shows you the diff between the working tree and the index,
> "git-diff --cached" shows the diff between the HEAD and the index, and
> "git-diff HEAD" shows you the diff between the working tree and the
> HEAD. To show that to the user, you need 3 commands, they will have to
> appear in the UI.

Well, that's one way to do it. It won't map well to xmtn. If instead
we have a good way to show all three diffs in one UI (which I think we
will), then we only need one DVC command, that runs git-diff three
times. Or "mtn automate inventory" once. And something else again for
bzr, hg, etc.

> Indeed, you really have two different flows depending on whether you
> intend to use "git-commit" (commit the content of the index) or
> "git-commit -a" (commit the content of the working tree, as other VCS
> would do).

I don't think monotone has that option, so making that available as a
git extension to the diff/status mode menu/keymap makes sense.

>> Or extend "diff table of contents" to really mean "status summary", as
>> I thought it did initially. Which would probably lead to not having a
>> separate dvc-status-mode.
>
> That's what I still think.

Actually, I like Christians's summary, which leads to three modes,
each much smaller than the current diff-mode.

But we need to actually do the work to find out :).

I have published my current DVC tree, at
http://www.stephe-leake.org/dvc/

The shared diff/status ewoc is not yet factored out; I need to get
some more unit tests working before I do that, so I can tell if I
break something.

-- 
-- Stephe

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

Reply via email to