netdev - Re: [PATCH] sctp: rfc conformance fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200810221601.27588.jk@ozlabs.org>
Date:	Wed, 22 Oct 2008 16:01:27 +1100
From:	Jeremy Kerr <jk@...abs.org>
To:	David Miller <davem@...emloft.net>
Cc:	mbizon@...ebox.fr, netdev@...r.kernel.org
Subject: Re: [PATCH] sctp: rfc conformance fixes

Hi,

> Jeremy, patchwork doesn't try to interpret the subject line
> at all does it?  My impression is that it simply looked for
> patches in the email posting content and that's it.

That's correct - patchwork uses the content of the mail to determine if 
it contains a patch, not the subject.

Patchwork does make a few modifications to the subject though - mostly 
treatment of []-enclosed prefixes. For example, it removes [PATCH] from 
the subject line - if it's in patchwork, it's a patch :).

So, in this case, the following subjects:

 [RFC] fix breakage
 [PATCH,RFC] fix breakage
 [RFC,PATCH] fix breakage
 [PATCH/RFC] fix breakage

will all be normalised to:

 [RFC] fix breakage

Cheers,

Jeremy

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html