mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 17:59:26 +0700	[thread overview]
Message-ID: <ZaJtDozZOgARzVRh@archie.me> (raw)
In-Reply-To: <2024011338-flammable-zoology-4686@gregkh>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

On Sat, Jan 13, 2024 at 09:44:00AM +0100, Greg Kroah-Hartman wrote:
> On Sat, Jan 13, 2024 at 01:59:47PM +0700, Bagas Sanjaya wrote:
> > That is, the submitter must send the full series, right? Why not partial
> > like above?
> 
> What can anyone do with a partial patch series?  Why would anyone who
> sent that think it would be material that anyone else should do work for
> them and review it when they aren't even sending the whole series?

IMO people will question why there is partial series submitted (and where the
missing patches are) and then ignore it if it becomes a pattern on submitter
side.

> 
> I'm confused as to why you would think that would be acceptable?  What
> are you really asking here?  Hypotheticals only go so far, please point
> at a real instance and we can talk about it there.

Honestly just to scratch my itch.

Thanks for the reply.

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2024-01-13 10: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
2024-01-13  8:44     ` Greg Kroah-Hartman
2024-01-13 10:59       ` Bagas Sanjaya [this message]

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=ZaJtDozZOgARzVRh@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®