On 19 March 2010 07:37, Daniel Näslund <dan...@longitudo.com> wrote: > Btw, other diffs I've found between entries and db handling of > revisions: (i) A missing dir has no revision value in the entries code, > but it has in the db.
Cool, so no real backwards compat problems there. If all else fails, we can check the 'missing' state and erase the revision number before passing on to callers-from-the-past. But I expect it to just sort itself out. > (ii) A file copied from foreign url to a wc has > the revision number set to its value in the foreign repo, although it is > locally added w/o history in this wc and thus should have 0. That's for > the entries. The db sets it to -1. Perfect. I never thought of copies from *foreign* repositories. So the db acts as if it was a normal add, not a copy, which is correct. ~Neels
