{"thread":{"id":"61034","subject":"[PATCH] gitcli: drop mention of “non-dashed form”","startedAt":"2024-03-01T18:06:12Z","lastAt":"2024-03-01T18:35:13Z","messageCount":2,"participants":["Kristoffer Haugsbakk","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"489746","messageId":"5b34bc4e22816f7f19bd26c15a08fe4c749b72f8.1709316230.git.code@khaugsbakk.name","threadId":"61034","inReplyTo":null,"subject":"[PATCH] gitcli: drop mention of “non-dashed form”","fromName":"Kristoffer Haugsbakk","fromEmail":"code@khaugsbakk.name","sentAt":"2024-03-01T18:05:53Z","receivedAt":"2024-03-01T18:06:12Z","isPatch":true,"sender":{"key":"code@khaugsbakk.name","avatar":"https://avatars.githubusercontent.com/u/2229597?v=4"},"body":"Git builtins used to be called like e.g. `git-commit`, not `git\ncommit` (*dashed form* and *non-dashed form*, respectively). The dashed\nform was deprecated in version 1.5.4 (2006). Now only a few commands\nhave an alternative dashed form when `SKIP_DASHED_BUILT_INS` is\nactive.[1]\n\nThe mention here is from 2f7ee089dff (parse-options: Add a gitcli(5) man\npage., 2007-12-13), back when the deprecation was relatively\nrecent. These days though it seems like an irrelevant point to make to\nbudding CLI scripters—you don’t have to warn against a style that\nprobably doesn’t even work on their git(1) installation.\n\n† 1: 179227d6e21 (Optionally skip linking/copying the built-ins,\n    2020-09-21)\n\nSigned-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>\n---\n\nNotes (series):\n    Now:\n    \n    ```\n    $ git grep --files-with-matches 'dashed form'\n    Documentation/RelNotes/1.5.4.txt\n    Documentation/RelNotes/2.16.0.txt\n    Makefile\n    t/README\n    ```\n    \n    For 179227d6e21 (Optionally skip linking/copying the built-ins,\n    2020-09-21):\n    \n    (sorry for the resend; I sent to my test address first)\n    \n    Cc: Johannes Schindelin <johannes.schindelin@gmx.de>\n\n Documentation/gitcli.txt | 3 ---\n 1 file changed, 3 deletions(-)\n\ndiff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt\nindex e5fac943227..7c709324ba9 100644\n--- a/Documentation/gitcli.txt\n+++ b/Documentation/gitcli.txt\n@@ -81,9 +81,6 @@ you will.\n Here are the rules regarding the \"flags\" that you should follow when you are\n scripting Git:\n \n- * It's preferred to use the non-dashed form of Git commands, which means that\n-   you should prefer `git foo` to `git-foo`.\n-\n  * Splitting short options to separate words (prefer `git foo -a -b`\n    to `git foo -ab`, the latter may not even work).\n \n-- \n2.44.0.106.g650c15c891b\n\n"},{"id":"489755","messageId":"xmqqy1b14x7n.fsf@gitster.g","threadId":"61034","inReplyTo":"5b34bc4e22816f7f19bd26c15a08fe4c749b72f8.1709316230.git.code@khaugsbakk.name","subject":"Re: [PATCH] gitcli: drop mention of “non-dashed form”","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-03-01T18:35:08Z","receivedAt":"2024-03-01T18:35:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Kristoffer Haugsbakk <code@khaugsbakk.name> writes:\n\n> ... These days though it seems like an irrelevant point to make to\n> budding CLI scripters—you don’t have to warn against a style that\n> probably doesn’t even work on their git(1) installation.\n\nIt is very true.  It is still technically correct that you should\nprefer spelling \"git cat-file\" instead of \"git-cat-file\", as the\nlatter may not work for you at all ;-).\n\n\n"}]}