On Mon, Mar 10, 2014 at 7:28 PM, Will Parsons <varro@nodomain.invalid>wrote:
> the main repository into the two secondary ones, but is it possible to
> then make branches B & C private retroactively? The documentation
> only mentions creating a private branch with the first commit.
>
If i'm not sorely mistaken, once content is made public, it can never again
be made private. Certain operations (e.g. tagging) take care to ensure that
public content does not refer to private content (because that would break
a sync). e.g. when tagging private content, the tag is automatically marked
as private as well. Once it's out there (public), "you can't stop the
signal."
> Also, the documentation says on one hand that creating a private
> branch results in a new branch named "private", which would seem to
> imply there can be only one private branch, but then later implies
> that there can be more than one ("You can remove all private
> branches..."). Can anyone clarify the situation?
>
This works for me:
stephan@host:~/cvs/fossil/x]$ history | tail
526 f open ../x.fsl
527 f set autosync 0
528 echo '#!!!' >> Makefile
529 f ci --private --branch p1 -m p1
530 f co trunk
531 echo '#!!!!!' >> Makefile
532 f ci --private --branch p2 -m p2
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
