On Wed, Dec 16, 2015 at 4:12 PM, <to...@acm.org> wrote: > > Hmm.. If one can create a private branch, do all draft work there and when done merge to trunk (or other non-private branch), then sync with the main repo, the main repo will not contain any traces of the private branch (with the draft work). Am I correct?
That seems to be the case based on my limited testing earlier today. > So, if then the local repo is deleted and a new one created by cloning the main repo, we end up with the desired effect: a repo that does not include any ‘bloat’ from the private work. That sounds correct. > But, since many people (myself including) seem to like the idea of draft work that once merged into mainstream branches should no longer take up space (forever) in the repo, and given that the above procedure actually achieves this goal, wouldn’t be nicer to have an explicit command (or option to existing command) to purge a private branch at the local level? >From http://fossil-scm.org/xfer/doc/trunk/www/private.wiki: > You can remove all private branches from a repository using this command: > fossil scrub --private > Note that the above is a permanent and irreversible change. You will be asked to confirm before continuing. Once the private branches are removed, they cannot be retrieved (unless you have synced them to another repository.) So be careful with the command. I just tried it and it worked. Also included is a warning that it is all or nothing. You can scrub all private or no private, but not one or some private (unless one or some are equal to all). :) SDR
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
