{"thread":{"id":"59980","subject":"Bug Report - Git does not require a space between shorthand flags and the commit-message","startedAt":"2023-07-13T13:25:08Z","lastAt":"2023-07-14T00:48:31Z","messageCount":2,"participants":["uxecw","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"479458","messageId":"fcdf19b3-269b-aa9f-38c2-d0f775524a89@student.kit.edu","threadId":"59980","inReplyTo":null,"subject":"Bug Report - Git does not require a space between shorthand flags and the commit-message","fromName":"uxecw","fromEmail":"uxecw@student.kit.edu","sentAt":"2023-07-13T13:04:37Z","receivedAt":"2023-07-13T13:25:08Z","isPatch":false,"sender":{"key":"uxecw@student.kit.edu","avatar":null},"body":"Thank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\nRebasing.\nI entered `git commit —amend` (one hypen istead of two) accidently and \nit passed as defacto `git commit —all —message \"end\"`.\nI think because of the missing space git should have rejected the given \ninput.\n\nWhat did you expect to happen? (Expected behavior)\nInput should have been rejected\n\nWhat happened instead? (Actual behavior)\n`git commit —all —message \"end\"`\n\nWhat's different between what you expected and what actually happened?\n\nAnything else you want to add:\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.34.1\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nuname: Linux 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC \nWed Jun 21 15:35:31 UTC 2 x86_64\ncompiler info: gnuc: 11.3\nlibc info: glibc: 2.35\n$SHELL (typically, interactive shell): /bin/bash\n\n\n[Enabled Hooks]\nnot run from a git repository - no hooks to show\n\n"},{"id":"479500","messageId":"ZLCbWn2qXZhmf8XD@tapette.crustytoothpaste.net","threadId":"59980","inReplyTo":"fcdf19b3-269b-aa9f-38c2-d0f775524a89@student.kit.edu","subject":"Re: Bug Report - Git does not require a space between shorthand flags and the commit-message","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2023-07-14T00:48:26Z","receivedAt":"2023-07-14T00:48:31Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2023-07-13 at 13:04:37, uxecw wrote:\n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n> \n> What did you do before the bug happened? (Steps to reproduce your issue)\n> Rebasing.\n> I entered `git commit —amend` (one hypen istead of two) accidently and it\n> passed as defacto `git commit —all —message \"end\"`.\n> I think because of the missing space git should have rejected the given\n> input.\n> \n> What did you expect to happen? (Expected behavior)\n> Input should have been rejected\n> \n> What happened instead? (Actual behavior)\n> `git commit —all —message \"end\"`\n\nI believe this is standard Unix behaviour.  One can combine\nsingle-character options, including a final single-character option that\ntakes an argument, and the argument can be appended to the option.\n\nFor example, I frequently type \"git commit -svS\", and I could well type\n\"git commit -svS0223b187\" (my OpenPGP key ID).  That also works\nsimilarly with OpenSSH: the command \"ssh -CoUser=foo server\" works just\nfine.\n\nSo I think it's best for Git to preserve the existing behaviour since\nit's standard for other tools as well (and, I believe, the\nPOSIX-mandated behaviour).\n-- \nbrian m. carlson (he/him or they/them)\nToronto, Ontario, CA\n"}]}