On Mon, Mar 10, 2014 at 2:46 PM, Stephan Beal <[email protected]> wrote:
> > On Mon, Mar 10, 2014 at 7:28 PM, Will Parsons <[email protected]>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. > Once you push content into the cloud, you can not call it back. It's out there. Trying make a branch private after it has already synced is like closing the door to the chicken coop after the chickens have all already decamped. But as long as you haven't synced, I think you can make a branch private simply by setting the "private" tag. fossil tag add --raw --propagate private $first-check-of-private-branch -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
