Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Hi, > > On Sat, 27 Oct 2007, Sergei Organov wrote: > >> It seems options parsing is somewhat broken in git-tag: >> >> $ git tag -a -m"Annotated tag" annotated-tag >> usage: git-tag [-n [<num>]] -l [<pattern>] | [-a | -s | -u <key-id>] [-f | -d | -v] [-m <msg> | -F <file>] <tagname> [<head>] >> $ git tag -a -m "Annotated tag" annotated-tag >> $ git --version >> git version 1.5.3.4 >> >> This is inconsistent with, say, "git commit", that groks -m"Message" >> (without space after -m) just fine. > > As it happens, we are in the middle of adding our own option parser which > probably solves the issue. Can you please retest when we have that, and > use it in builtin-tag? I'm 100% sure there will be no inconsistencies once you unify options parsing among the tools, but I won't refrain from re-testing this anyway. -- Sergei. - 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
