From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id C142E1F5AE for ; Tue, 4 May 2021 20:35:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231986AbhEDUgJ (ORCPT ); Tue, 4 May 2021 16:36:09 -0400 Received: from smtp.hosts.co.uk ([85.233.160.19]:35785 "EHLO smtp.hosts.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231576AbhEDUgH (ORCPT ); Tue, 4 May 2021 16:36:07 -0400 Received: from host-92-1-139-132.as13285.net ([92.1.139.132] helo=[192.168.1.37]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1le1l8-0000Iv-Bn; Tue, 04 May 2021 21:35:10 +0100 Subject: Re: Git commit allow empty docs unclear To: Cristiana Man , git@vger.kernel.org References: From: Philip Oakley Message-ID: <4c7e5858-7694-efe3-d048-da35fc8cba3a@iee.email> Date: Tue, 4 May 2021 21:35:10 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-GB Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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