From: Roman Gushchin <roman.gushchin@linux.dev>
To: John Hubbard <jhubbard@nvidia.com>, Miguel Ojeda <ojeda@kernel.org>
Cc: rust-for-linux@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>,
lyude@redhat.com
Subject: Re: Maybe make Sashiko emails opt-in please?
Date: Thu, 23 Apr 2026 22:16:07 +0000 [thread overview]
Message-ID: <7ia4tst18grc.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <971a606f-3319-46c5-ad84-a250f8044d53@nvidia.com>
Hey!
I'm totally happy to disable email delivery for rust-for-linux if Miguel
is onboard - I generally rely on maintainers for the decision how to use
Sashiko or not use at all. I have obviously zero interest in pushing it
against developers will, however it's hard to achieve a full consensus
on anything in a large group of people, so I have to prioritize maintainers
opinion.
Miguel, what do you think? I can keep you on cc, so that you will be
receiving reviews, but nobody else. That would be my personal preference
in this case.
Otherwise:
Unfortunately I can't provide Sashiko as a free service for an open set
of kernel engineers, I simple don't have a big enough budget to cover
associated compute costs. If there is some company which is willing to
cover it, we can probably set something up via LF - Sashiko as a project
belongs to LF.
I try to make it easy to set up local/corporate instances and also
try to make it work with any LLM providers. I personally only have
access to Gemini, so I'm somewhat limited in testing here and rely on
other contributors.
Thanks
next prev parent reply other threads:[~2026-04-23 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 1:10 Maybe make Sashiko emails opt-in please? lyude
2026-04-23 1:48 ` Alexandre Courbot
2026-04-23 20:24 ` John Hubbard
2026-04-23 22:16 ` Roman Gushchin [this message]
2026-04-24 23:22 ` Miguel Ojeda
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=7ia4tst18grc.fsf@castle.c.googlers.com \
--to=roman.gushchin@linux.dev \
--cc=acourbot@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@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