* Git commit allow empty docs unclear
@ 2021-05-04 18:31 Cristiana Man
2021-05-04 20:31 ` Felipe Contreras
2021-05-04 20:35 ` Philip Oakley
0 siblings, 2 replies; 3+ messages in thread
From: Cristiana Man @ 2021-05-04 18:31 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Git commit allow empty docs unclear
2021-05-04 18:31 Git commit allow empty docs unclear Cristiana Man
@ 2021-05-04 20:31 ` Felipe Contreras
2021-05-04 20:35 ` Philip Oakley
1 sibling, 0 replies; 3+ messages in thread
From: Felipe Contreras @ 2021-05-04 20:31 UTC (permalink / raw)
To: Cristiana Man, git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Git commit allow empty docs unclear
2021-05-04 18:31 Git commit allow empty docs unclear Cristiana Man
2021-05-04 20:31 ` Felipe Contreras
@ 2021-05-04 20:35 ` Philip Oakley
1 sibling, 0 replies; 3+ messages in thread
From: Philip Oakley @ 2021-05-04 20:35 UTC (permalink / raw)
To: Cristiana Man, git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-05-04 20:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-04 18:31 Git commit allow empty docs unclear Cristiana Man
2021-05-04 20:31 ` Felipe Contreras
2021-05-04 20:35 ` Philip Oakley
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).