On 2017-02-04 15:01:43, Jan Danielsson wrote: > (...) > So when you do your initial clone, it only downloads some metadata > about what files exist in the repository, but not the contents of them. > When you open a file, the vfs will fetch the file for you. > > Say a project has a doc/ directory which is unrelated to the build > process, and there are 200MB worth of documents in there. A person who > just wants to build the project probably doesn't want to download all > those docs, so they just kick off the build without touching the files > in doc/. > > Like I said, I only skimmed a few seconds so I could be way off, but > that's what it looked like to me. > > If it is what I think it is: With all these indexing tools out > there, scanning every file it finds, I wonder how useful this feature > really is?
It's clearcase all over again. I don't remember the specifics (it's nearly 20 years ago I was working on a clearcase VFS checkout under solaris), but we (clearcase users) preferred the explicit nature of CVS back then. IIRC, shared access to the VFS was leading to all sorts of kinky side-effects. Personally, I'd neither use a git, nor a fossil virtual file system, much less when it requires an up to date Windows 10 installation and a MS git binary. Regards, -Martin _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
