When a submodule cannot be described, doing a "git submodule status" on
the supermodule produces unnecesary and scary output, for example:
fatal: cannot describe 'cac575f1bccf0c6942d11962cf4d44ba974d3e8e'
cac575f1bccf0c6942d11962cf4d44ba974d3e8e megaco/megaco_tipc
Where it should just show:
cac575f1bccf0c6942d11962cf4d44ba974d3e8e megaco/megaco_tipc
The culprit (after manual inspection of git log) seems to be commit
a2cf9f4.
This patch fixes this by making git submodule aware of that behaviour
change.
Signed-off-by: Alberto Bertogli <albertito@xxxxxxxxx>
---
git-submodule.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-submodule.sh b/git-submodule.sh
index a6aaf40..5e8b84f 100755
--- a/git-submodule.sh
+++ b/git-submodule.sh
@@ -315,7 +315,7 @@ set_name_rev () {
cd "$1" && {
git describe "$2" 2>/dev/null ||
git describe --tags "$2" 2>/dev/null ||
- git describe --contains --tags "$2"
+ git describe --contains --tags "$2" 2>/dev/null
}
) )
test -z "$revname" || revname=" ($revname)"
--
1.5.4.1.1279.g0d205f-dirty
-
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
