Richard Hipp wrote: > --===============0402830886== > Content-Type: multipart/alternative; boundary=089e016347a4d508c804f4451ff0 > > --089e016347a4d508c804f4451ff0 > Content-Type: text/plain; charset=ISO-8859-1 > > 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
This is purely a private project, so synching isn't an issue. I did what you suggested above, and am not sure how to interpret the results. I kind of assumed that the command would result in the tag "private" being added to every commit in the branch, but I don't see that in the timeline. What I do see is a new event added to the timeline: Edit [ec9d5eef305a3c02]: Add propagating "private". and in the initial check-in for the branch: private propagates to descendants added by ... Does this mean the branch will be treated as a private branch now, and if I sync to the main repository, the branch will not be synched? -- Will _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
