On Mon, Mar 28, 2011 at 10:37 PM, Nolan Darilek <[email protected]>wrote:
> More important, what *are* subrepositories? Entirely separate fossils > linked to the main repository, or separate namespaces for tags and such > in a single fossil? Or the ability to open a nested repository in another? > > Wondering if I'll need to migrate some of my multi-repository fossils to > a new format somehow. > > > On 03/28/2011 09:36 PM, Michael Richter wrote: > > I just saw an intriguing message in the timeline. "Leaf: Merge the > sub-repo > > capability into trunk." I can't find anywhere in the help, the fossil > docs > > nor in the wiki that talks about this. How does one use this new > sub-repo > > capability? > Here's my conjecture, based on how Git does submodules, without having looked at the Fossil subrepository code... I'm guessing that in the repository, a submodule might be represented by an artifact that contains an identification of the subrepository, plus the identifier of the checked-out tree for that repository, with a path in a manifest identifying the location of the subrepository in the directory tree. A subrepository could be identified by a Fossil URL or maybe requiring it to be a sibling of the current repository -- a URL is nice, because it provides a way to retrieve it when you clone the parent repository. On disk, a subrepository might be checked-out as a subdirectory of the current check-out (corresponding to the entry in the manifest). Bill
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
