On Wed, Mar 5, 2014 at 2:21 AM, Chad Perrin <c...@apotheon.net> wrote:
> 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. > Presumably the server admin (you?) would be the one creating new repositories on the server, so would be able to use "fossil clone" or "fossil import" either via SSH or directly on the server. I tried experimenting with the --incremental option. It appears to work for keeping a Fossil repository up to date after the initial import. I don't know if that is an intended limitation or a bug. Right now, I don't have more time to experiment with it as it is not a feature I use.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
