# Git commit allow empty docs unclear 3 messages from 2021-05-04 to 2021-05-04. Participants: Cristiana Man, Felipe Contreras, Philip Oakley. Thread: https://gitlist.dev/t/55618 ## Cristiana Man, 2021-05-04 18:31 Subject: Git commit allow empty docs unclear Message-ID: URL: https://gitlist.dev/e/CAL2wJUAk50O-iSH9PEewYHwE9tV-TZZerqd1Eh9OTQfWBkmCgA%40mail.gmail.com ``` Hi The documentation for Git commit --allow-empty option (https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty) contains the acronym SCM which is confusing to me. Do you mean Software Configuration Management, Source Control Management or Source Code Management? Clarifications are appreciated! -- Kind regards, Cristiana Man ``` ## Felipe Contreras, 2021-05-04 20:31 Subject: RE: Git commit allow empty docs unclear Message-ID: <6091af2cc6dd_b34a820889@natae.notmuch> URL: https://gitlist.dev/e/6091af2cc6dd_b34a820889%40natae.notmuch In-Reply-To: ``` Cristiana Man wrote: > The documentation for Git commit --allow-empty option > (https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty) > contains the acronym SCM which is confusing to me. > Do you mean Software Configuration Management, Source Control > Management or Source Code Management? The documentation is on git-SCM.com, also, there's a glossary [1]: SCM: Source code management (tool). Cheers. [1] https://git-scm.com/docs/gitglossary -- Felipe Contreras ``` ## Philip Oakley, 2021-05-04 20:35 Subject: Re: Git commit allow empty docs unclear Message-ID: <4c7e5858-7694-efe3-d048-da35fc8cba3a@iee.email> URL: https://gitlist.dev/e/4c7e5858-7694-efe3-d048-da35fc8cba3a%40iee.email In-Reply-To: ``` hi Cristiana, On 04/05/2021 19:31, Cristiana Man wrote: > Hi > > The documentation for Git commit --allow-empty option > (https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---allow-empty) > contains the acronym SCM which is confusing to me. > Do you mean Software Configuration Management, Source Control > Management or Source Code Management? > Clarifications are appreciated! Yes, all of them ;-) Basically the Git (Linux codebase) philosophy is to always have meaningful changes, with meaningful commit change messages. When Git was being developed (i.e. being implemented in many other code bases) there was a lot of migration of from old "documentation" systems, which often had 'cruft' where options were needed to allow such empty commits, and the common TLA (three Letter abbreviation) of the time 'SCM' could cover all of them. The key aspect is that they were 'foreign' to the Git ecosystem. Hope that helps. > -- > > Kind regards, > Cristiana Man -- Philip ```