I've a need to do this as well, and have been thinking about using git to store the overall project and using separate fossil repositories for each submodule.
This would involve duplicating the repository data in a submodule as it would be stored both in fossil and in git - but I think this would work out, as the workflow would involve working in fossil 90% of the time and then commiting everything to git for a submodule release. Because of the fossil-git integration I'm hoping that any rough edges could be automated with scripts. On 5 February 2011 01:36, Ron Wilson <[email protected]> wrote: > On Fri, Feb 4, 2011 at 7:01 PM, Ondrej Nemecek > <[email protected]> wrote: > > So there is only one possible solution - open and close repossitories > > as needed (top level repository and subrepositories). > > > > Have anybody better idea? >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
