Now that's interesting - so using nesting it should be possible to nicely work with shared components for multiple projects. A set up like this should be possible:
You can have one folder with all the shared components, each component in it's own folder and versioned as a separate Fossil project, then for each application you work on you just check out the component into a subfolder of the project to keep all the components in sync. On 10 June 2011 22:59, Ron Wilson <[email protected]> wrote: > I have not had problems, not even with nested working copies (That is, > a working copy of a project contained within a working copy of a > different project). >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
