On Aug 18, 2016, at 1:12 AM, Stephan Beal <sgb...@googlemail.com> wrote: > > git combines clone/open into a single operation
Fossil could as well. If you either don’t give a clone target or that target is a directory instead of a file, it could save the repo file to .fslrepo or similar at the root of either CWD or the clone target directory, then open that repo in-place. > each clone is tied to a single open copy, whereas fossil separates them That would be one good reason to continue to recommend giving a repo file as the second argument to clone instead of using it in git-like fashion. I don’t argue for this to make git users happy, but instead to make Fossil more like Subversion, where there is no additional step required check out a new repository. > i'm guessing that few people ever use 'close’? I’ve found it useful just prior to rm -r’ing a Fossil checkout for any reason, to ensure that Fossil forgets about that checkout. I recall drh saying that Fossil will eventually realize it has stale info in its ~/.fossil repo and forget it, but I’m certain I’ve seen it keep such info long past when it should before. Perhaps that’s been patched now, but ever since running into that, I’ve always formally closed a checkout before nuking it. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
