From: Junio C Hamano <gitster@pobox•com>
To: "Michal Suchánek" <msuchanek@suse•de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
"Erik Cervin Edin" <erik@cervined•in>,
"Christian Couder" <christian.couder@gmail•com>,
jurgen_gjoncari@icloud•com, git <git@vger•kernel.org>
Subject: Re: Make commit messages optional
Date: Mon, 11 Apr 2022 14:09:54 -0700 [thread overview]
Message-ID: <xmqq1qy3gwd9.fsf@gitster.g> (raw)
In-Reply-To: <20220411181819.GF163591@kunlun.suse.cz> ("Michal Suchánek"'s message of "Mon, 11 Apr 2022 20:18:19 +0200")
Michal Suchánek <msuchanek@suse•de> writes:
>> In any case, "--allow-empty-messages" exists, and that is where we
>> draw the line. We will not bend over backwards beyond it.
>
> Isn't special-casing the empty message bending over backwards to some
> other influence instead?
Not at all.
Even though the low level plumbing commands try to be accomodating
to people with different tastes, the Porcelain layer is opinionated
itself, and tries to give defaults that encourage good development
practice to interactive users. There is no need for some other
influence---we chose to reject creating commits with empty messages
to prevent mistakes that novices may find hard to recover from,
and that's final.
next prev parent reply other threads:[~2022-04-11 21:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 3:35 Make commit messages optional jurgen_gjoncari
2022-04-08 8:02 ` Christian Couder
2022-04-08 11:26 ` Ævar Arnfjörð Bjarmason
2022-04-08 19:25 ` Erik Cervin Edin
2022-04-11 10:24 ` Ævar Arnfjörð Bjarmason
2022-04-11 17:59 ` Junio C Hamano
2022-04-11 18:18 ` Michal Suchánek
2022-04-11 21:09 ` Junio C Hamano [this message]
2022-04-08 8:15 ` Philip Oakley
2022-04-08 14:32 ` Phillip Susi
2022-04-08 22:30 ` brian m. carlson
2022-04-08 23:32 ` rsbecker
2022-04-09 11:32 ` Michal Suchánek
2022-04-10 13:59 ` Tao Klerks
2022-04-10 15:00 ` rsbecker
2022-04-10 15:18 ` rsbecker
2022-04-10 16:27 ` Tao Klerks
2022-04-13 5:40 ` Jonathan Nieder
2022-04-11 9:04 ` demerphq
2022-04-11 11:35 ` rsbecker
2022-04-11 10:19 ` Ævar Arnfjörð Bjarmason
2022-04-11 12:39 ` Tao Klerks
2022-04-11 18:09 ` Junio C Hamano
2022-04-11 18:15 ` Michal Suchánek
2022-04-11 18:23 ` tytso
2022-04-11 20:10 ` Ævar Arnfjörð Bjarmason
2022-04-14 14:46 ` Theodore Ts'o
2022-04-14 16:43 ` Ævar Arnfjörð Bjarmason
2022-04-14 17:25 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1qy3gwd9.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=erik@cervined$(echo .)in \
--cc=git@vger$(echo .)kernel.org \
--cc=jurgen_gjoncari@icloud$(echo .)com \
--cc=msuchanek@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox