linux-kernel - Re: Deliberately sending partial patch sets?

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: <ZaI04-HDHbBxKYbS@archie.me>
Date: Sat, 13 Jan 2024 13:59:47 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jakub Kicinski <kuba@...nel.org>
Subject: Re: Deliberately sending partial patch sets?

On Fri, Jan 12, 2024 at 08:37:10PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Jan 12, 2024 at 09:20:45PM +0700, Bagas Sanjaya wrote:
> > Hi,
> > 
> > Let's say that there is a contributor who wish to send a patch set (e.g.
> > 20-30 patches in the series) to LKML. But instead of sending the full
> > series, he either do one of the following:
> > 
> > * Send only the cover letter (analogous to movie trailers)
> > * Send only a few arbitrary patches in a series that are most important
> >   (e.g. patch [01,04,11,18,23/30]) (analogous to match highlights)
> > * Send only the first few patches in a series (i.e. subject of one of
> >   patches says [09/30]) (analogous to sample book chapters)
> > 
> > The rest of patches are behind closed doors (i.e. not sent), possibly
> > behind charm-priced (pay)walls.
> > 
> > Is the submission like above acceptable (when in review)?
> 
> No, kernel development is done in public.

That is, the submitter must send the full series, right? Why not partial
like above?

Confused...

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)