Linux Media Controller development
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Derek Barbosa <debarbos@redhat.com>,
	Matthieu Baerts <matttbe@kernel.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Steven Rostedt <rostedt@goodmis.org>,
	users@kernel.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Stephen Finucane <stephenfin@redhat.com>
Subject: Re: Linking Patchwork with Sashiko?
Date: Tue, 14 Jul 2026 19:00:54 -0700	[thread overview]
Message-ID: <4928C919-7999-4E76-ADCB-F8643FED105B@linux.dev> (raw)
In-Reply-To: <20260715005909.GF1656185@killaraus.ideasonboard.com>

> On Jul 14, 2026, at 5:59 PM, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> 
> On Tue, Jul 14, 2026 at 10:55:42PM +0000, Roman Gushchin wrote:
>> Mauro Carvalho Chehab writes:
>>>> On Mon, 13 Jul 2026 12:41:20 +0300 Laurent Pinchart wrote:
>>>>>>> Individuals can set their
>>>>>>> spam filters up if they don't want to get these emails, I can't control
>>>>>>> it. Providing individual authors an option "I don't want my patches
>>>>>>> to be reviewed" sound strange to me. It's like "I don't want my patches
>>>>>>> to be tested by unit tests".  
>>>>>> 
>>>>>> I agree with you, and, on my head, not sending e-mails to the author
>>>>>> is a clear violation to one of the most basic net etiquette rule on
>>>>>> mailing lists: any replies to posts there should reach the author.  
>>>>> 
>>>>> I don't know where that one comes from.
>>>>> 
>>>>> What happened to this other "most basic rule" that subscription to
>>>>> services that deliver e-mails should be opt-in ?
>>> 
>>> Replying to an e-mail is not subscribing to a service. It is the
>>> author's right to know if one replies publicly to his e-mails.
>>> Explicitly removing him from the C/C of such replies is a violation
>>> of his rights.
>>> 
>>> On other words, it is implicit that, if you post an e-mail, you'll be
>>> expecting actions or answers to it.
>>> 
>>> Now, if one really doesn't really want to receive e-mails from a
>>> particular sender, a block list solves it. Alternatively, a way to
>>> opt-out is welcomed.
>>> 
>>> See, this is different than adding someone to a mailing list without
>>> his consent: On such case, people receive e-mails unrelated to their
>>> preferences. For those, opt-in is the right net etiquette.
>> 
>> I agree with this.
>> 
>> But also just practically: if someone who opted out from sashiko emails
>> posts a patch and sashiko finds say a critical issue, do we expect the
>> maintainer to go and manually check each time whether the author opted
>> out and forward the review?
> 
> I expect maintainers who want to act on sashiko reviews to triage and
> verify them first before bothering authors, yes. I believe we should
> follow the first two recommendations of the Software Freedom Conservancy
> on using LLM-backed generative AI systems for FOSS contributions ([1]).
> 
> [1] https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html

I think it makes the point of sashiko - helping maintainers - unachievable. If the point to not use
LLMs in general, let’s discuss this, not how to make each use case more complex.

It seems like [1]  expresses a very anti-LLM position in general, which I can understand and I agree 
with some of concerns. But I think it’s up to project leaders to decide if Linux in general  takes this 
position and my take so far is that the answer is not.

Thanks

  reply	other threads:[~2026-07-15  2:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260528144627.1ae09ff2@foz.lan>
     [not found] ` <1372F826-5513-4EB2-AE27-1DC0D2DE0AEB@linux.dev>
     [not found]   ` <20260529083100.6710b6cd@foz.lan>
     [not found]     ` <20260529083801.2c7e8990@foz.lan>
     [not found]       ` <ahmwUk0uXTkdwohf@debarbos-thinkpadt14gen5.rmtusma.csb>
2026-05-30  8:30         ` Linking Patchwork with Sashiko? Mauro Carvalho Chehab
2026-05-30 15:57           ` Roman Gushchin
2026-05-30 18:00             ` Mauro Carvalho Chehab
2026-05-30 18:49               ` Mauro Carvalho Chehab
2026-05-30 18:53                 ` Mauro Carvalho Chehab
2026-06-02 15:51                   ` Derek Barbosa
2026-06-02 16:51                     ` Mauro Carvalho Chehab
2026-06-02 18:39                       ` Jason Gunthorpe
2026-06-02 20:29                         ` Mauro Carvalho Chehab
2026-06-02 20:13                     ` Roman Gushchin
2026-06-02 20:39                       ` Mauro Carvalho Chehab
2026-06-02 20:44                         ` Roman Gushchin
2026-06-02 23:50                         ` Matthieu Baerts
2026-06-03  3:35                           ` Mauro Carvalho Chehab
2026-06-03  3:49                             ` Roman Gushchin
2026-06-04  6:52                           ` Mauro Carvalho Chehab
2026-06-07 17:56                             ` Mauro Carvalho Chehab
2026-06-30 20:32                               ` Derek Barbosa
2026-07-10  5:45                                 ` Mauro Carvalho Chehab
2026-07-10  6:39                                   ` Mauro Carvalho Chehab
2026-07-11  1:01                                     ` Roman Gushchin
2026-07-13  7:55                                       ` Mauro Carvalho Chehab
2026-07-13  9:41                                         ` Laurent Pinchart
2026-07-13 20:04                                           ` Mauro Carvalho Chehab
2026-07-14 22:55                                             ` Roman Gushchin
2026-07-15  0:59                                               ` Laurent Pinchart
2026-07-15  2:00                                                 ` Roman Gushchin [this message]
2026-07-15  3:06                                                   ` Linus Torvalds
2026-07-15  7:59                                                   ` Jacopo Mondi
2026-07-15  8:40                                                     ` Mauro Carvalho Chehab
2026-07-15  3:54                                                 ` Theodore Tso
2026-07-15  7:13                                                   ` Mauro Carvalho Chehab

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=4928C919-7999-4E76-ADCB-F8643FED105B@linux.dev \
    --to=roman.gushchin@linux.dev \
    --cc=debarbos@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=konstantin@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stephenfin@redhat.com \
    --cc=users@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