Junio C Hamano wrote: > And a subproject commit, unless it contains subsubproject, would > look like just an ordinary commit. Its tree would match the > entry in the tree the toplevel commit at the path in "bind" line > of the top-level commit. > > Some reading material, from newer to older: > > * http://www.kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=Subpro.txt > > This talks about the overall "vision" on how the user-level > interaction might look like, with a sketch on how the core-level > would help Porcelain to implement that interaction. Most of the > core-level support described there is in the "bind commit" > changes, except "update-index --bind/-unbind" to record the > information on bound subprojects in the index file. By the way, this file talks about (1) "using"/"userspace"/"embedder" subproject holding 'appliance/', and toplevel (master) holding toplevel Makefile, or (2) 'using' subproject holding both 'appliance/' and toplevel Makefile with the help of --exclude. Another option would be to have only "embedded"/"used"/"requirement" be subproject holding 'kernel-2.6', and 'appliance/' hold by toplevel (master) commit. Perhaps not the best solution for 'kernel + userspace tools' example, but might be better workflow for 'application + library' or 'application + engine' example. -- 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