-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ah, OK, if it's fixed then awesome. This particular project was converted from Git a couple months back, so perhaps it was done without the fixed Fossil and got the old permissions.
Though I still wonder what's the justification for making Clone a separate permission. I mean, what's the point of checking out if you can't clone in the first place, or cloning if you can't check out to update that clone later? On 01/18/2011 01:26 PM, Joerg Sonnenberger wrote: > On Tue, Jan 18, 2011 at 12:40:21PM -0600, Nolan Darilek wrote: >> I've used Fossil on various open source projects, and keep discovering >> that I need to permit the nobody user to clone these repositories--this, >> despite the fact that it has the checkout permission by default. > > How recent is your fossil? I remember some change for exactly this issue > a while ago. > > Joerg > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0167oACgkQIaMjFWMehWL/sACfXfpLU+QCmE/+obBDfNmKQt2/ /sMAmweUZD0GiCyYpLaQP0O+vL9wkAGm =xZge -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
