Ran across some submodule behavior that seems wrong to me. I don't have the chops to fix the issues, so I thought I'd just point them out with some unit tests. Patch 1 tests the case where "submodule add" fails if the path to the submodule repo is relative (i.e. starts with "../"). This currently fails with "remote (origin) does not have a url defined in .git/config". Maybe there's a reason to fail? If so, a better error message would be appreciated. Patch 2 exposes an anomaly in "submodule status", which reports that a submodule is OK even though it has deleted files. "git status" inside the submodule (and in the super-repo) both identify any deleted files, but "submodule status" doesn't prefix the submodule's HEAD SHA-ID with a "+". (ps. I didn't sign-off these two patches, since they're just failing unit tests. Should I sign-off on them?) M. -- 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