Re: [fossil-users] How to make a private branch public?
On Nov 24, 2013, at 12:41 , Rolf Ade wrote: Andy Bradford amb-fos...@bradfords.org writes: Thus said Rolf Ade on Sat, 23 Nov 2013 21:36:02 +0100: My test repository is a very simple one, only a few test commits. Is this way - delete from private with an sqlite tool on the repository database - really a working way without sideeffects, to make private branches public? Perhaps you could merge the private branch into the non-private branch? Yes, I know that this is possible. But I'm asking for more. I not only want to make the result of my work within the private branch public, I want to disclose the whole history of that work. There is no way to do this right now. Current implementation of private branches is more of a hack. A proper solution would allow push/pull of a specific branch. Which was proposed many times, but never fully implemented. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to make a private branch public?
Thus said Rolf Ade on Sun, 24 Nov 2013 12:41:37 +0100: But I'm asking for more. I not only want to make the result of my work within the private branch public, I want to disclose the whole history of that work. Instead of a private branch, make a public branch in a private clone with autosync disabled. Then when you are ready, do a push. Andy -- TAI64 timestamp: 40005292319e ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to make a private branch public?
Thus said Rolf Ade on Sun, 24 Nov 2013 12:41:37 +0100: But I'm asking for more. I not only want to make the result of my work within the private branch public, I want to disclose the whole history of that work. In addition to my last suggestion, to reduce the risk of accidental synchronization before the work on the branch is ready, you could unset remote-url in the clone. fossil remote-url off Then use fossil pull --once http://user@remote/fossil To keep your private clone in sync. You could also utilize the newly added fossil clone --once http://user@remote/fossil Once done you'll also need to specify the Fossil user since it will not be set. Then use fossil pull as before. Andy -- TAI64 timestamp: 400052923b04 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
