On Mon, Feb 6, 2012 at 1:53 PM, Lluís Batlle i Rossell <vi...@viric.name> wrote: > On Mon, Feb 06, 2012 at 01:07:30PM -0500, Ron Wilson wrote: >> >> Mark your branch private. >> >> Anything you want to push can then be merged into a non-private branch. > > Ah, well, that's fine for personal work. I meant a bit how to do private > collaborative work over a public fossil base. Sorry that I did not state all I > had in mind clear enough.
So you want to have a "restricted" branch that is shared between a subset of the developers? You could setup a second shared repository and only allow access to the select group, Then have a script that sets your group branch private, pushes to the public repository, then unsets the private attribute on the group branch. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
