On 2024-01-16 05:05, Vyacheslav Yurkov wrote:
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?
It shouldn't be considered a strict requirement, as it's going to be
difficult for Patchtest to correctly identify which pages do and don't
need more explanation.
If you want to completely avoid that feedback, then the solution for now
is to re-state the shortlog as a one-line commit description.
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
<[email protected]> 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 (#193870):
https://lists.openembedded.org/g/openembedded-core/message/193870
Mute This Topic: https://lists.openembedded.org/mt/103758512/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
