Josef Weidendorfer wrote: > An example for such an attribute would be a subproject name/ID. > An argument for this: The user should be able to specify some policies > for submodules, like "do not clone/checkout this submodule". But the > path where the submodule resides in a given commit is not useful here, > as a submodule can reside at different paths in the history of the > supermodule. > I mentioned this briefly on another strand of this thread, but I think that the simplest way to do this would be to just make refs/subproject/* populate itself sensibly when you commit in the superproject. I mentioned refs/subprojects/path/branch before, but I think it would probably be the sort of thing that should be in the .git/config Sam. - To unsubscribe from this list: 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