On Wed, Mar 05, 2014 at 01:40:49AM -0500, Ron Wilson wrote: > On Tue, Mar 4, 2014 at 7:24 PM, Chad Perrin <[email protected]> wrote: > > > Both of those solutions would surely work in this case (as long as the > > incremental option works on the server, but not in cases where the same > > would be done by someone with commit access but no SSH filesystem/shell > > access (which is likely in future cases). > > > If you mean using a hosting service, then I would think the service either > provides SSH access or a way transfer existing project repositories to the > service's hosts, possibly providing a means to clone from your local Fossil > repository to the server.
I'm talking about a distributed team, where not everyone has SSH shell access or the ability to directly change anything on the filesystem, but they all have commit access to a specific set of repositories. This means, for instance, that they could clone from, and sync with, an existing repository -- but not all could create or delete entire repositories. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
