list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <>
To: Cristiana Man <>,
Subject: RE: Git commit allow empty docs unclear
Date: Tue, 04 May 2021 15:31:40 -0500	[thread overview]
Message-ID: <6091af2cc6dd_b34a820889@natae.notmuch> (raw)
In-Reply-To: <>

Cristiana Man wrote:
> The documentation for Git commit --allow-empty option
> (
> 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, also, there's a glossary [1]:

  SCM: Source code management (tool).



Felipe Contreras

  reply	other threads:[~2021-05-04 20:31 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 [this message]
2021-05-04 20:35 ` Philip Oakley

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:

  List information:

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

  git send-email \
    --in-reply-to=6091af2cc6dd_b34a820889@natae.notmuch \ \ \ \

* 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

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).