{"thread":{"id":"55618","subject":"Git commit allow empty docs unclear","startedAt":"2021-05-04T18:31:39Z","lastAt":"2021-05-04T20:35:16Z","messageCount":3,"participants":["Cristiana Man","Felipe Contreras","Philip Oakley"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"423603","messageId":"CAL2wJUAk50O-iSH9PEewYHwE9tV-TZZerqd1Eh9OTQfWBkmCgA@mail.gmail.com","threadId":"55618","inReplyTo":null,"subject":"Git commit allow empty docs unclear","fromName":"Cristiana Man","fromEmail":"man.cristiana1@gmail.com","sentAt":"2021-05-04T18:31:22Z","receivedAt":"2021-05-04T18:31:39Z","isPatch":false,"sender":{"key":"man.cristiana1@gmail.com","avatar":null},"body":"Hi\n\nThe documentation for Git commit --allow-empty option\n(https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty)\ncontains the acronym SCM which is confusing to me.\nDo you mean Software Configuration Management, Source Control\nManagement or Source Code Management?\nClarifications are appreciated!\n--\n\nKind regards,\nCristiana Man\n"},{"id":"423608","messageId":"6091af2cc6dd_b34a820889@natae.notmuch","threadId":"55618","inReplyTo":"CAL2wJUAk50O-iSH9PEewYHwE9tV-TZZerqd1Eh9OTQfWBkmCgA@mail.gmail.com","subject":"RE: Git commit allow empty docs unclear","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-05-04T20:31:40Z","receivedAt":"2021-05-04T20:31:48Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Cristiana Man wrote:\n> The documentation for Git commit --allow-empty option\n> (https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty)\n> contains the acronym SCM which is confusing to me.\n> Do you mean Software Configuration Management, Source Control\n> Management or Source Code Management?\n\nThe documentation is on git-SCM.com, also, there's a glossary [1]:\n\n  SCM: Source code management (tool).\n\nCheers.\n\n[1] https://git-scm.com/docs/gitglossary\n\n-- \nFelipe Contreras\n"},{"id":"423610","messageId":"4c7e5858-7694-efe3-d048-da35fc8cba3a@iee.email","threadId":"55618","inReplyTo":"CAL2wJUAk50O-iSH9PEewYHwE9tV-TZZerqd1Eh9OTQfWBkmCgA@mail.gmail.com","subject":"Re: Git commit allow empty docs unclear","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2021-05-04T20:35:10Z","receivedAt":"2021-05-04T20:35:16Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"hi Cristiana,\n\nOn 04/05/2021 19:31, Cristiana Man wrote:\n> Hi\n>\n> The documentation for Git commit --allow-empty option\n> (https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty)\n> contains the acronym SCM which is confusing to me.\n> Do you mean Software Configuration Management, Source Control\n> Management or Source Code Management?\n> Clarifications are appreciated!\n\nYes, all of them ;-)\n\nBasically the Git (Linux codebase) philosophy is to always have\nmeaningful changes, with meaningful commit change messages.\n\nWhen Git was being developed (i.e. being implemented in many other code\nbases) there was a lot of migration of from old \"documentation\" systems,\nwhich often had 'cruft' where options were needed to allow such empty\ncommits, and the common TLA (three Letter abbreviation) of the time\n'SCM' could cover all of them. The key aspect is that they were\n'foreign' to the Git ecosystem.\n\nHope that helps.\n\n> --\n>\n> Kind regards,\n> Cristiana Man\n--\nPhilip\n"}]}