Re: Using different default-directory and relative paths in VC, Was: Re: bug#21383

[Stefan Monnier]

>> Sorry, I didn't realize you were talking about vc-state.  No I guess
>> vc-state would have to keep working with absolute file names (tho it
>> could be extended to also accept relative file names).
> It was just an example.  Would vc-state keep working with absolute file
> names, but vc-working-revision start only accepting relative ones?

I guess all those functions which are part of the API exposed by VC to
external packages would need to preserve support for absolute file
names, yes.

>> I'd expect that the caller should be able to easily arrange for each
>> file in the list to *already* be relative to default-directory, so
>> there's no need to look for the common parent.
> If the relative file names start with "../", the result is pointless:

I explicitly ruled them out in my earlier definition of "relative file names".


        Stefan