From: Philip Oakley <philipoakley@iee.email>
To: jurgen_gjoncari@icloud.com, git@vger.kernel.org
Subject: Re: Make commit messages optional
Date: Fri, 8 Apr 2022 09:15:01 +0100 [thread overview]
Message-ID: <5d6df8fa-eaea-4ead-e966-8efe60784409@iee.email> (raw)
In-Reply-To: <7ED89912-2E10-4356-9C61-14B90EC0719C@icloud.com>
Hi Jurgen
On 08/04/2022 04:35, jurgen_gjoncari@icloud.com wrote:
> I think that often commit messages are unnecessary. I propose that by default a user should be able to commit without a message.
>
> I don't think this would be a problem from the UX point of view, because a user could get a lot of information about a change, from the history of the GitHub repository, such as from the time of change, and seeing the diff.
>
> I think that making commit messages options wouldn't even be a problem for retro compatibility because the feature would remain still functional for those who would want to use it.
Isn't this an ideal candidate for an alias that simply passes in the
empty message?
However, it's worth reviewing and doing a retrospective about commit
messages and who they are there to inform.
They (these supposedly informative messages) used to frustrate me many
years ago. I already _knew_ what I was doing, and it was 'obvious', what
even needed saying (so say nothing).
The Git project's style has been informative in showing how to provide a
well focussed concise message that should be understandable to others,
to your future self, and help clarify one's current understanding of the
problem at hand. Often the last point will mean one upgrades the code to
meet the real need.
--
Philip
next prev parent reply other threads:[~2022-04-08 8:16 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
2022-04-08 8:15 ` Philip Oakley [this message]
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
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=5d6df8fa-eaea-4ead-e966-8efe60784409@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=jurgen_gjoncari@icloud.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).