Re: Crazy idea: changes in WC should share an API with changes in repository
From: Julian Foad <julianfoad_at_apache.org>
Date: Fri, 09 Nov 2018 11:47:15 +0000
Branko Čibej wrote:
I don't think that's an accurate description. The WC layers provide the repository base revisions of nested copies, like a cache of the referenced disparate bits of the repository history. The FS txn also supports nested copies, storing references to their bases in other revisions where the data can be found. In each cases the "modification" layer is built by reference to one main base plus zero or more copy-bases. In each case the relevant "base" API must support access to both the main base (which is mixed-rev in the case of WC) and those copy-bases.
> Also note that the working copy may have switched subtrees, or
Yes, "switched" comes under the head of "WC specifics".
> I understand these APIs could be reused for both shelving and
Absolutely! In order to prove an implementation of the "WC modifications editor" I would expect to convert more or less *all* of the existing client commands to make their WC changes through this editor.
> Also is this "just"
I would expect to deprecate swathes of the existing WC APIs.
-- - JulianReceived on 2018-11-09 12:47:23 CET
This is an archived mail posted to the Subversion Dev mailing list.