On Wed, May 27, 2015 at 7:25 AM, Richard Hipp <[email protected]> wrote:
> The other approach would be to deny "push" privileges to the students > and force them to email in "bundles" that contain their changes, to be > added back to the trunk administratively by the instructor. That's a > lot more work on the instructor's part Given that the instructor will be reviewing changes before committing them to trunk, I don't think this would really be a lot more work. Also, from my observation, this seems to be a variant of common practice. Specifically, other than a small number of "core devs", projects only accept patches or "pull requests", which the core devs then review and integrate.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
