On Tue, Mar 04, 2014 at 09:56:31PM -0500, Richard Hipp wrote: > On Tue, Mar 4, 2014 at 9:45 PM, Chad Perrin <[email protected]> wrote: > > > Is there a "good" way to do the same thing Git's "submodule" command > > does, to allow multiple repositories to be used to compose a single, > > larger project source tree? > > > > > The only thing (currently) like this in Fossil is the "fossil open > --nested" command, which allows you to create a checkout for repository > nested inside a checkout for another repository. (Normally, if you try to > do "fossil open" while you are within another check-out, the open fails > with an error.) > > A nested check-out does NOT keep track of which versions of which > repositories are associated with each check-in. Nor are there convenient > commands that fetch an automatically open nested check-outs. The only > thing this allows is for you to construct a tree of checkouts. > > But maybe that is enough for what you are trying to do. I dunno....
Someone I know was asking about it. I wondered if there was more available than --nested for that, for purposes of things like being able to automate cloning of "submodules" or at least getting a canonical list of "submodules" for a project to help keep a distributed team on the same page in terms of managing the whole source tree split across repositories, if only for the purpose of being able to advise my acquaintance intelligently. Thanks. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
