On Wed, Aug 31, 2011 at 7:37 PM, Nolan Darilek <no...@thewordnerd.info>wrote:
> I'd be interested in this one too. Why might you want one and not the > other? Or, more accurately, why isn't checkout sufficient, since presumably > a clone is a checkout of everything? Because when I was originally writing Fossil, I thought it would be convenient to be able to restrict Clone as a means of limiting bandwidth usage. Sure, you could always get the same information by doing multiple checkouts, but I thought if it were hard, there would be fewer attempts. As it turns out, the clone protocol is so efficient that restricting clone has not really been necessary. > > > On 08/30/2011 03:55 PM, Lluís Batlle i Rossell wrote: > >> Hello, >> >> I never understood enough the difference between the 'checkout' and the >> 'clone' >> user permissions in fossil. >> >> Can someone explain why would someone have the cases of "checkout and not >> clone" >> or "clone and not checkout"? >> >> Thank you, >> Lluís. >> ______________________________**_________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.**org <fossil-users@lists.fossil-scm.org> >> http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/** >> fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> >> > > ______________________________**_________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.**org <fossil-users@lists.fossil-scm.org> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
