On Sat, 13 Oct 2012 09:27:38 -0400 Richard Hipp <d...@sqlite.org> wrote:
> Brainstorm: A potential work-around > > Fossil actually uses multiple databases. Of interest to us are (1) > the repository database and (2) the ".fslckout" database which is > specific to an individual checkout of that repository. The > repository is persistent and long-lasting and needs to be "safe". The > check-out database lasts only for the lifetime of a local tree. I'm (again) reading all the Fossil docs and while being on 'private' page (http://fossil-scm.org/index.html/doc/trunk/www/private.wiki) I saw the following:"There is no mechanism in Fossil (currently) that allows you to push, pull, clone, sync, or scrub and individual private branch within a repository that contains multiple private branches. " so the above mentioned workaround could make it possible, to, at least, scrub individual private branches, right? Otoh, having mechanism to push/pull/clone/sync individual branches would make Fossil fall in the dream-land category. Sincerely, Gour -- Not by merely abstaining from work can one achieve freedom from reaction, nor by renunciation alone can one attain perfection. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
