On Sat, Feb 25, 2012 at 09:17, Richard Hipp <d...@sqlite.org> wrote: > > A key philosophical design principle of Fossil is "no erasures". This is > how business financial accounting is (or used to be) done. You write in > ink.
I am fine with this philosophy of "no-rewriting" of published history. And I am *not* asking for a "git rebase" equivalent. But I have to follow a work-flow that consists of a cascade of repositories. (1) PRV.fossil -- is my private repo where all my dirty laundry is stored (2) TEAM.fossil -- this is a place shared by the development team. Mistakes can be annotated as "mistake" and backed out as you said. (3) PUBLIC.fossil -- is a clean and shiny final result that must be devoid of all the crazy stuff from TEAM.fossil and PRV.fossil repos. So far I found no way to accomodate (1)->(2)->(3) cascading work-flow. Please, advice if I am missing something (I am a novice fossil user). Previous discussions on this list suggested a new feature [1] that would allow to push/pull individual leaves or branches. If implemented it would resolve my biggest grievance with fossil. [1] http://code.linuxfood.net/pub/repo/fossil-limsync --Leo-- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
