Missing signoff in the arm-soc tree
Mark Brown
maintainerCommit
3edcea7f0413e ("Merge branch 'arm/fixes' into for-next")
is missing a Signed-off-by from its committer (and also isn't showing up as a merge).
Mark Brown
maintainerQuoted 6 lines · Mark Brown
Commit
3edcea7f0413e("Merge branch 'arm/fixes' into for-next")is missing a Signed-off-by from its committer (and also isn't showing up as a merge).
This issue (and the matching author signoff) is still present today.
Mark Brown
maintainerQuoted 9 lines · Mark Brown
Quoted 6 lines · Mark Brown
Commit
3edcea7f0413e("Merge branch 'arm/fixes' into for-next")is missing a Signed-off-by from its committer (and also isn't showing up as a merge).
This issue (and the matching author signoff) is still present today.
These issues are *still* present today. It's making noise whenever I check -next for ongoing issues, it'd be good if the branch could be rebuilt.
Quoted 6 lines · Mark Brown
Quoted 5 lines · Mark Brown
Quoted 4 lines · Mark Brown
Commit
3edcea7f0413e("Merge branch 'arm/fixes' into for-next")
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
is missing a Signed-off-by from its committer (and also isn't showing up as a merge).
This issue (and the matching author signoff) is still present today.
These issues are *still* present today. It's making noise whenever I check -next for ongoing issues, it'd be good if the branch could be rebuilt.
I assume you hit this on the branch I pushed out earlier today, which started fresh from 7.3 with just a single merge. I've amended that commit with an S-o-b now, but I'm not sure if that is what you are asking.
When you write "and also isn't showing up as a merge", do you mean your script has an exception for merge commits to not need S-o-b but fails to detect this one as a merge? I see that about half the merges in linux-next (including your daily merges) are not signed off, so I'm not sure if we are all doing this wrong the same way, or if there is a different problem with the soc tree.
Arnd
Mark Brown
maintainerQuoted 10 lines · Arnd Bergmann
Quoted 3 lines · Mark Brown
These issues are *still* present today. It's making noise whenever I check -next for ongoing issues, it'd be good if the branch could be rebuilt.
I assume you hit this on the branch I pushed out earlier today, which started fresh from 7.3 with just a single merge. I've amended that commit with an S-o-b now, but I'm not sure if that is what you are asking.
It is in whatever was there when I fetched the trees this morning which was some time before I finished the merge and ran the summary stuff so you may have updated it later.
Quoted 6 lines
When you write "and also isn't showing up as a merge", do you mean your script has an exception for merge commits to not need S-o-b but fails to detect this one as a merge? I see that about half the merges in linux-next (including your daily merges) are not signed off, so I'm not sure if we are all doing this wrong the same way, or if there is a different problem with the soc tree.
As indicated in the original mail and repeated followups the relevant commit is 3edcea7f0413e84863300998ad3838eb87e6fca7 which looks from the changelog like it was originally a merge but is not described as such in the git metadata, it is just an apparently empty commit with a single parent with a suspiciously similar changelog. My theory was that something had gone wrong with a rebase or scripting. I only check for signoff problems on non-merge commits, merge commits are ignored since they are not normally signed off.