From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: Deliberately sending partial patch sets?
Date: Sat, 13 Jan 2024 13:59:47 +0700 [thread overview]
Message-ID: <ZaI04-HDHbBxKYbS@archie.me> (raw)
In-Reply-To: <2024011247-caregiver-compacted-2e6b@gregkh>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-13 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 14:20 Bagas Sanjaya
2024-01-12 19:37 ` Greg Kroah-Hartman
2024-01-13 6:59 ` Bagas Sanjaya [this message]
2024-01-13 8:44 ` Greg Kroah-Hartman
2024-01-13 10:59 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZaI04-HDHbBxKYbS@archie.me \
--to=bagasdotme@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®