On Tue, Jul 15, 2014 at 9:37 AM, Gour <g...@atmarama.net> wrote: > Afaik, there was some talk inthe past about having some kind of hg-like > bundle which could be sent via email & applied... >
At least from the web UI, Fossil can create patch files from commits. As best I can determine from a description of "hg bundle", a patch file provides similar functionality. > I'm asking 'cause I do not envision to give commit access to every new > dev coming to the project. While Fossil's unified view philosophy has a lot of merits, it does impose extra requirements for developer discipline. Even when a contribution is pulled by a core developer, the contributor needs to have used a uniquely named branch. With a patch file (or series of patch files), the differences can be applied to a checkout of the appropriate commit then the changes reviewed. To be honest, for accepting contributions from outside the core team, I would clone my repository, then pull the contribution into the clone. That way, any side effects of the pull would be easier to contain. But, I have never had contributions from outside the core team of any of the projects I've worked on, so I can't yet say what would work best for me.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
