Den 22.11.2022 16.51, skrev Konstantin Ryabitsev: > On Mon, Nov 21, 2022 at 07:13:28PM +0100, Noralf Trønnes wrote: >>> Otherwise, you might consider using: >>> https://b4.docs.kernel.org/en/latest/contributor/send.html#authenticating-with-the-web-submission-endpoint >>> >> >> That's an interesting option. I did briefly look at b4 a few months back >> but it looked like it was under heavy development so I figured I'd wait >> before trying it out. I think I'll give b4 a spin to see how it works, I >> wonder how it handles patch changelogs. > > I'd be happy to help set this up for you -- to date, this service hasn't been > used beyond a few test posts. > Ok, I'll give it a try. I have now prepared the patchset, generated a key and can now do: b4 send -o The first thing that strikes me is that everyone mentioned in one of the patches get the entire patchset, even stable@xxxxxxxxxxxxxxx (cc'ed in a fixes patch). The first patch touches a core file and as a result a few drivers, so I've cc'ed the driver maintainers in that patch, but now they get the entire patchset where 5 of 6 patches is about a driver that I maintain. So from their point of view, they see a patchset about a driver they don't care about and a patch touching a core file, but from the subject it's not apparent that it touches their driver. I'm afraid that this might result in none of them looking at that patch. In this particular case it's not that important, but in another case it might be. As for the setting up the web endpoint, should I just follow the b4 docs on that? I use b4 version 0.10.1, is that recent enough? Noralf.
