Sam Vilain wrote: > Junio C Hamano wrote: >>> 3. sub-projects >>> >>> In this case, the commit on the "main" commit line would have a >>> "prior" link to the commit on the sub-project. The sub-project >>> would effectively be its own head with copied commits objects on >>> the main head. >>> >> >>You say you can have only one "prior" per commit, which makes >>this unsuitable to bind multiple subprojects into a larger >>project (the earlier "bind" proposal allows zero or more). > > It would still support that. Each commit to the sub-project involves a > change to the tree of the "main" commit line (a copy of the commit into > a sub-directory of it). The advantage is that the "tree" in the main > commit is the combined tree, you don't need to treat the case specially > to just get the contents out. As far as I understand, for subproject commit "bind" link (and perhaps the keyword/name "link" or "ref" would be better than "related") point to other subprojects commits (trees), while the Sam's "prior (3)" example link would point to the toplevel project (gathering all subprojects) commit, and it would probably be named/noted "toplevel", not "prior". Am I correct? -- Jakub Narebski Warsaw, Poland - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html