{"thread":{"id":"10485","subject":"Minor inconsistency: \"git tag\" requires space after -m.","startedAt":"2007-10-27T11:55:01Z","lastAt":"2007-10-27T13:14:03Z","messageCount":3,"participants":["Sergei Organov","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"57349","messageId":"ffv8ul$5a2$1@ger.gmane.org","threadId":"10485","inReplyTo":null,"subject":"Minor inconsistency: \"git tag\" requires space after -m.","fromName":"Sergei Organov","fromEmail":"osv@javad.com","sentAt":"2007-10-27T11:55:01Z","receivedAt":"2007-10-27T11:55:01Z","isPatch":false,"sender":{"key":"osv@javad.com","avatar":null},"body":"Hello,\n\nIt seems options parsing is somewhat broken in git-tag:\n\n$ git tag -a -m\"Annotated tag\" annotated-tag\nusage: git-tag [-n [<num>]] -l [<pattern>] | [-a | -s | -u <key-id>] [-f | -d | -v] [-m <msg> | -F <file>] <tagname> [<head>]\n$ git tag -a -m \"Annotated tag\" annotated-tag\n$ git --version\ngit version 1.5.3.4\n\nThis is inconsistent with, say, \"git commit\", that groks -m\"Message\"\n(without space after -m) just fine.\n\n-- \nSergei.\n"},{"id":"57353","messageId":"Pine.LNX.4.64.0710271347510.4362@racer.site","threadId":"10485","inReplyTo":"ffv8ul$5a2$1@ger.gmane.org","subject":"Re: Minor inconsistency: \"git tag\" requires space after -m.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-10-27T12:48:44Z","receivedAt":"2007-10-27T12:48:44Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 27 Oct 2007, Sergei Organov wrote:\n\n> It seems options parsing is somewhat broken in git-tag:\n> \n> $ git tag -a -m\"Annotated tag\" annotated-tag\n> usage: git-tag [-n [<num>]] -l [<pattern>] | [-a | -s | -u <key-id>] [-f | -d | -v] [-m <msg> | -F <file>] <tagname> [<head>]\n> $ git tag -a -m \"Annotated tag\" annotated-tag\n> $ git --version\n> git version 1.5.3.4\n> \n> This is inconsistent with, say, \"git commit\", that groks -m\"Message\"\n> (without space after -m) just fine.\n\nAs it happens, we are in the middle of adding our own option parser which \nprobably solves the issue.  Can you please retest when we have that, and \nuse it in builtin-tag?\n\nThanks,\nDscho\n"},{"id":"57354","messageId":"ffvdir$g2n$1@ger.gmane.org","threadId":"10485","inReplyTo":"Pine.LNX.4.64.0710271347510.4362@racer.site","subject":"Re: Minor inconsistency: \"git tag\" requires space after -m.","fromName":"Sergei Organov","fromEmail":"osv@javad.com","sentAt":"2007-10-27T13:14:03Z","receivedAt":"2007-10-27T13:14:03Z","isPatch":false,"sender":{"key":"osv@javad.com","avatar":null},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n> Hi,\n>\n> On Sat, 27 Oct 2007, Sergei Organov wrote:\n>\n>> It seems options parsing is somewhat broken in git-tag:\n>> \n>> $ git tag -a -m\"Annotated tag\" annotated-tag\n>> usage: git-tag [-n [<num>]] -l [<pattern>] | [-a | -s | -u <key-id>] [-f | -d | -v] [-m <msg> | -F <file>] <tagname> [<head>]\n>> $ git tag -a -m \"Annotated tag\" annotated-tag\n>> $ git --version\n>> git version 1.5.3.4\n>> \n>> This is inconsistent with, say, \"git commit\", that groks -m\"Message\"\n>> (without space after -m) just fine.\n>\n> As it happens, we are in the middle of adding our own option parser which \n> probably solves the issue.  Can you please retest when we have that, and \n> use it in builtin-tag?\n\nI'm 100% sure there will be no inconsistencies once you unify options\nparsing among the tools, but I won't refrain from re-testing this\nanyway.\n\n-- \nSergei.\n"}]}