What's incorrect, the documentation, or the implementation ? >From private.wiki:
After additional work, one might desire to publish the changes associated with a private branch. The usual way to do this is to merge those changes into a public branch. For example: <blockquote><pre> fossil update trunk fossil merge private fossil commit </pre></blockquote> The private branch remains private. (There is no way to convert a private branch into a public branch.) But all of the changes associated with the private branch are now folded into the public branch and are hence visible to other users of the project. On 1/5/16, Richard Hipp <d...@sqlite.org> wrote: > On 1/5/16, bch <brad.har...@gmail.com> wrote: >> I just did another pull, and the branch tags showed up, so @drh, I >> think your rebuild helped somewhat. Now to find out how the repo got >> into it's "broken" state in the first place. >> > > The rebuild didn't help. It was my manual DELETE of the offending > entry in the PRIVATE table of the database that fixed it. But that > entry will reappear at the next rebuild, I suspect. > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
