Martin von Zweigbergk 187ba9430a working_copy: rename to local_working_copy ... It's about time we make the working copy a pluggable backend like we have for the other storage. We will use it at Google for at least two reasons: * To support our virtual file system. That will be a completely separate working copy backend, which will interact with the virtual file system to update and snapshot the working copy. * On local disk, we need to tell our build system where to find the paths that are not in the sparse patterns. We plan to do that by wrapping the standard local working copy backend (the one moved in this commit), writing a symlink that points to the mainline commit where the "background" files can be read from. Let's start by renaming the exising implementation to `local_working_copy`.		2023-10-07 08:19:03 -07:00
..
src	working_copy: rename to local_working_copy	2023-10-07 08:19:03 -07:00
Cargo.toml