-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello. I'm using Fossil on a small project I started recently and it seems like an interesting concept. There is one thing about which I'm unclear, however.
The reference states that multiple working trees can be tied to a single repository. How exactly is this done, and I'm wondering if it is what I think it is? I have a group of tangentially related projects that all use a core library and have various interdependencies. Even though they serve different niches (core library, web service and mobile app using aspects of said core library, etc.) I would still benefit from tracking them under a single issue tracker/wiki hierarchy. Sometimes an issue that manifests in one app actually originates in the core library. I was thinking of doing a multi-project Redmine installation for this but never quite set it up, partially because of the trouble and partially because I vastly prefer distributed development. Is that what the multiple working tree support is intended to accomplish, or am I very confused about what a working tree means in this context? :) I'm also wondering if this approach is how wiki pages, issues, etc. are versioned such that it's possible to edit the wiki/HTML/CSS as plain text? This looks like an interesting concept. Not sure if I like it yet but I'm willing to give it a shot. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyAU0gACgkQIaMjFWMehWJtQgCeLhvPfUvWyc12wiNEOW9ZuvUS 6TwAn0bgQ2kSPC5BCpx3+m3iU5P1nM4q =NOfi -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
