On Wed, 27 May 2015 19:24:38 +0200, Ron W <[email protected]> wrote:
(Sorry, accidently clicked the "Send" button when trying to click the
"unfold" icon in the editor.)
On Wed, May 27, 2015 at 6:10 AM, j. van den hoff
<[email protected]>
wrote:
the "request to work on branch" is the catch: he wants to ensure that
students can never mess up trunk
You could achieve a "safety net", but preventing a student from
intentionally pushing changes to trunk is possible.
Set trunk as private. Then students clone the master repo with "fossil
clone --private URL localrepo.fossil". Then when they create their dev
branches, they "fossil publish mybranch".
In fact, your friend could provide a script to do the clone, start the
branch and publish the branch.
thanks. I will notify my colleague of this proposal. maybe that fits his
needs.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
