Matthieu Moy <[EMAIL PROTECTED]> writes: > Stephen Leake <[EMAIL PROTECTED]> writes: > >> First, I need to know what the letters in the 'status' field of a >> 'file element in dvc-diff-cookie mean, and update the backends (at >> least bzr and mtn) to respect the definitions. > > Historically, DVC (Xtla at that time) parsed and then reproduced the > output of "tla changes" and later "baz changes". > > There's no formal definition of it, and the fact that this is > represented with letters was a mistake. Internally, DVC should work > with symbols, and then the printer could give letters.
I agree with that. But we have to start with the code we have now; I'm not up to rewriting everything at this point. If we use letters for now, and gradually convert code to use dvc-diff-ewoc->status, then at some point we can switch to using symbols. On the other hand, maybe it's not all that much work to just go straight to symbols. I guess I'll look at that some more. Is the list of symbols I suggested a good start? > Indeed, to be general, it should be a list of symbols, because a file > can, for example, be both modified and renamed. Ah. If the user edits a file, and then renames it, and then runs dvc-status, won't it show up as 'missing old-name' and 'unknown new-name'? Then the user will want to tell dvc that it should instead be 'modified' and 'renamed'. I guess at that point status would need to be a list. -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
