git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Cristiana Man <man.cristiana1@gmail.com>, git@vger.kernel.org
Subject: Re: Git commit allow empty docs unclear
Date: Tue, 4 May 2021 21:35:10 +0100	[thread overview]
Message-ID: <4c7e5858-7694-efe3-d048-da35fc8cba3a@iee.email> (raw)
In-Reply-To: <CAL2wJUAk50O-iSH9PEewYHwE9tV-TZZerqd1Eh9OTQfWBkmCgA@mail.gmail.com>

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

      parent reply	other threads:[~2021-05-04 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4c7e5858-7694-efe3-d048-da35fc8cba3a@iee.email \
    --to=philipoakley@iee.email \
    --cc=git@vger.kernel.org \
    --cc=man.cristiana1@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).