public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "Oscar Megia López" <megia.oscar@gmail.com>,
	kernel-janitors@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	"Dan Carpenter" <error27@gmail.com>
Subject: Re: Contributing subsequent patch versions
Date: Sun, 30 Jul 2023 12:12:42 +0200	[thread overview]
Message-ID: <2023073013-remix-outscore-c4f9@gregkh> (raw)
In-Reply-To: <85938916-305c-c8b9-89db-45e522616526@web.de>

Hi,

This is the semi-friendly patch-bot of Greg Kroah-Hartman.

Markus, you seem to have sent a nonsensical or otherwise pointless
review comment to a patch submission on a Linux kernel developer mailing
list.  I strongly suggest that you not do this anymore.  Please do not
bother developers who are actively working to produce patches and
features with comments that, in the end, are a waste of time.

Patch submitter, please ignore Markus's suggestion; you do not need to
follow it at all.  The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and
inability to adapt to feedback.  Please feel free to also ignore emails
from them.

thanks,

greg k-h's patch email bot

  parent reply	other threads:[~2023-07-30 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 18:06 I need help to send v2 patch on linux-ext4 at vger.kernel.org Oscar Megia López
     [not found] ` <8ef54195-4102-0c6c-e14d-efc9bc45cddc@web.de>
2023-07-28  6:22   ` Contributing subsequent patch versions Oscar Megia López
2023-07-28 18:10     ` Theodore Ts'o
2023-07-30  6:23       ` Oscar Megia López
     [not found]         ` <85938916-305c-c8b9-89db-45e522616526@web.de>
2023-07-30 10:12           ` Greg KH [this message]
     [not found]     ` <61a79836-3981-b6e0-cbbf-fe03507dbea4@web.de>
2023-07-28 18:36       ` Oscar Megia López
2023-07-28 19:59         ` Theodore Ts'o
2023-07-30  7:10           ` Oscar Megia López
     [not found]         ` <27a41740-9cdd-2adf-f3cc-1f9a2d9f2ed1@web.de>
2023-07-30  7:56           ` Oscar Megia López

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=2023073013-remix-outscore-c4f9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Markus.Elfring@web.de \
    --cc=error27@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=megia.oscar@gmail.com \
    --cc=tytso@mit.edu \
    /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