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
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
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
On 16/01/2024 10:08:50+0100, Alexander Kanavin wrote:
> No.
Why not?
>
> Alex
>
> On Tue, 16 Jan 2024 at 09:53, Vyacheslav Yurkov wrote:
> >
> > Is that a strict requirement now even for trivial patches?
> >
> > Slava
> >
> > On 16.01.2024 09:45, patcht...@automation.yoctoproject.org wrote:
>
No.
Alex
On Tue, 16 Jan 2024 at 09:53, Vyacheslav Yurkov wrote:
>
> Is that a strict requirement now even for trivial patches?
>
> Slava
>
> On 16.01.2024 09:45, patcht...@automation.yoctoproject.org wrote:
> > Thank you for your submission. Patchtest identified one
> > or more issues with the
Is that a strict requirement now even for trivial patches?
Slava
On 16.01.2024 09:45, patcht...@automation.yoctoproject.org wrote:
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/v2-7-9-oeqa-selftest-recipetool-Move-create_go-test-to-a-proper-class.patch
FAIL: test commit message presence:
