[Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs?

Andrew Donnellan ajd at linux.ibm.com
Mon Jul 1 11:35:59 AEST 2019

On 1/7/19 2:01 am, Mauro Carvalho Chehab wrote:
> Em Sat, 29 Jun 2019 12:20:55 +0100
> Mark Brown <broonie at kernel.org> escreveu:
>> On Sat, Jun 29, 2019 at 09:18:28AM +0200, Takashi Iwai wrote:
>>> BTW, can the URL be reached from patchwork?  That'd be really handy.
>> Even better, could patchwork add it to the mboxes you download from it
>> like acks and so on?  Currently you can get the message ID so it's easy
>> to construct the link for things that are on LKML.
> I'm all for it, but the problem with patchwork is that the tool may be used
> on non-kernel development and/or the ML may not be in lore.
> Also, there are more than one patchwork instance. We use our own for
> Linux media (https://patchwork.linuxtv.org)[1].
> On media, patchwork is used for both Kernel development and VDR
> development (an userspace tool) - with is a completely unrelated
> project (with different people behind it - and even a different mailing
> list).
> So, whatever change at patchwork should be done in a way that the
> ML URL could be customized, and the new field would be added only
> if the URL is not blank.

[+ patchwork list]

I'll have a go at adding a project/list-specific archive prefix and 
exposing that in the web interface.

Regarding adding it to downloaded mboxes, if we do that I'd like it to 
be a separate option. A single patch can also land in patchwork multiple 
times via various lists, so the URL will depend on which project you're 
looking at.

Andrew Donnellan              OzLabs, ADL Canberra
ajd at linux.ibm.com             IBM Australia Limited

More information about the Patchwork mailing list