Wait, that's not exactly what I mean. Each of my private branches were originally created with this command line:
fossil commit -m "" --branch sue --private Note that I do give it a name and mark it as private. So perhaps --private only is the difference you're seeing. On Wed, Dec 16, 2015 at 5:23 PM, Scott Robison <sc...@casaderobison.com> wrote: > That is exactly what I mean. I'll see what I can do later to provide a > transcript. > > On Wed, Dec 16, 2015 at 5:18 PM, Warren Young <w...@etr-usa.com> wrote: > >> On Dec 16, 2015, at 4:58 PM, Scott Robison <sc...@casaderobison.com> >> wrote: >> > >> > On Wed, Dec 16, 2015 at 4:53 PM, Warren Young <w...@etr-usa.com> wrote: >> > >> > > the private branch is always called “private” >> > >> > I have a test repo at present with three private branches named test, >> bob, and sue. >> >> By “private branch” do you mean “f ci --private,” or something else, like >> running with autosync disabled, so that all new branches are created only >> in your private clone of the repo? >> >> Would you mind posting a session transcript that someone could paste into >> a terminal to recreate your test repo? >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > > -- > Scott Robison > > -- Scott Robison
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
