[fossil-users] documentation bug
In the help test for push, the description of the -R option reads: -R|--repository REPO Repository to pull into whereas I think it should read "repository to push from" or similar. -- Will ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git just got shallow and sparse clones
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
Re: [fossil-users] Git just got shallow and sparse clones
On 2017-02-04 14:07, Konstantin Khomoutov wrote: > On Fri, 3 Feb 2017 09:00:54 -0700 > Warren Youngwrote: > >> https://developers.slashdot.org/story/17/02/03/1427213/microsoft-introduces-gvfs-git-virtual-file-system > > Care to elaborate a bit? [---] Granted, I just skimmed a few seconds, but I got the feeling that the new feature makes it look like it has a bunch of stuff checked out when it really hasn't. And once you try to access files which haven't been fetched before, it fetches them for you. 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? -- Kind Regards, Jan ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git just got shallow and sparse clones
On Fri, 3 Feb 2017 09:00:54 -0700 Warren Youngwrote: > https://developers.slashdot.org/story/17/02/03/1427213/microsoft-introduces-gvfs-git-virtual-file-system Care to elaborate a bit? commit 016e6ccbe03438454777e43dd73d67844296a3fd Author: Johannes Schindelin Date: Mon Oct 30 20:09:29 2006 +0100 allow cloning a repository "shallowly" Available since v1.5. commit ed5336a7541e19b267de53afc8d15cffdbde8286 Author: Nguyễn Thái Ngọc Duy Date: Thu Aug 20 20:47:05 2009 +0700 Introduce "sparse checkout" Available since v1.7. The current stable Git version is 2.11. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users