From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: patchtest@automation.yoctoproject.org,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Patchtest results for [PATCH v2 7/9] oeqa/selftest/recipetool: Move create_go test to a proper class
Date: Tue, 16 Jan 2024 11:05:34 +0100 [thread overview]
Message-ID: <cc8df8ea-e8c6-4190-a02e-9ffcbfa7ab0b@gmail.com> (raw)
In-Reply-To: <CANNYZj90_-6AssGQLxc7tAqT24KDBMB5NPNpsD3g-XLOXc1sGg@mail.gmail.com>
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.belloni@bootlin.com> wrote:
>> On 16/01/2024 10:08:50+0100, Alexander Kanavin wrote:
>>> No.
>> Why not?
>>
next prev parent reply other threads:[~2024-01-16 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:45 Patchtest results for [PATCH v2 7/9] oeqa/selftest/recipetool: Move create_go test to a proper class patchtest
2024-01-16 8:53 ` Vyacheslav Yurkov
2024-01-16 9:08 ` [OE-core] " Alexander Kanavin
2024-01-16 9:28 ` Alexandre Belloni
2024-01-16 9:32 ` Alexander Kanavin
2024-01-16 10:05 ` Vyacheslav Yurkov [this message]
2024-01-16 17:39 ` Trevor Gamblin
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=cc8df8ea-e8c6-4190-a02e-9ffcbfa7ab0b@gmail.com \
--to=uvv.mail@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patchtest@automation.yoctoproject.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox