I also have the same opinion. What else am I supposed to write in the
body if it were merely a refactoring (function moved, renamed, etc), and
it's already described in the hearer?
Slava
On 16.01.2024 10:32, Alexander Kanavin wrote:
Because making it strict would only result in useless noise in the
commit logs. It's entirely valid to have changes that can fully be
described with a commit header. I see it as a notice to consider if
the commit message should be added, at the discretion of both
submitter and committer.
Alex
On Tue, 16 Jan 2024 at 10:28, Alexandre Belloni
<alexandre.bell...@bootlin.com> wrote:
On 16/01/2024 10:08:50+0100, Alexander Kanavin wrote:
No.
Why not?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193848):
https://lists.openembedded.org/g/openembedded-core/message/193848
Mute This Topic: https://lists.openembedded.org/mt/103758512/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
