{"thread":{"id":"13766","subject":"git describe","startedAt":"2008-06-02T17:25:48Z","lastAt":"2008-06-02T17:25:48Z","messageCount":1,"participants":["Michael Dressel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"78401","messageId":"alpine.LNX.1.10.0806021908210.3330@pollux","threadId":"13766","inReplyTo":null,"subject":"git describe","fromName":"Michael Dressel","fromEmail":"michaeltilodressel@t-online.de","sentAt":"2008-06-02T17:25:48Z","receivedAt":"2008-06-02T17:25:48Z","isPatch":false,"sender":{"key":"michaeltilodressel@t-online.de","avatar":null},"body":"Hi,\n\ngit describe does not seam to apply the pattern given by the --match \noption in case the tag is a soft one. Is that done intentionally?\n\nIn addition I wonder if it was possible to introduce an option that would \nshow all tags of a given commit, at least when --exact-match is specified \ntoo?\n\nAt the moment I'm using git log --decorate in a script to get the above\nresult. Part of the script looks something like this:\n\n\n  \t\tmytags=`git log --pretty=oneline --max-count=1\\\n  \t\t\t--decorate $commit\\\n  \t\t| awk '\n/.*\\/tags\\/V1\\..*/ {\n  \tsub(\"^.*[(]\",\"\")\n  \tgsub(\"tag: \",\"\")\n  \tsub(\"[)].*\",\"\")\n  \tgsub(\" \",\"\")\n\n\n  \tsplit($0, tl, \",\")\n  \tfor (var in tl)\n  \t{\n  \t\tif (tl[var] ~ /refs\\/tags/ && tl[var] ~ V1){\n  \t\t\tsub(\"refs/tags/\",\"\",tl[var])\n  \t\t\tprint tl[var]\n  \t\t}\n  \t}\n}\n'`\n\nSince that is quite clumsy. I would like to use git describe which\nalmost does what I need.\n\nCheers,\nMichael\n"}]}