Hi Quentin Schulz, On Friday, October 9th, 2026 at 4:57 AM, Quentin Schulz <[email protected]> wrote:
> Hi Rong An, > > On 10/8/26 4:40 PM, 安容 wrote: > > Hello Quentin Schulz, > > > > On Friday, October 2nd, 2026 at 5:37 PM, Quentin Schulz <[email protected]> > > wrote: > > > >> https://lore.kernel.org/u-boot/[email protected]/ > >> has the "via B4 Relay" I would expect when using the relay and there's > >> no To/Cc matching the rule above. Can you give it a try? Maybe that just > >> works? > > > > That's seems a good idea. I will try it at first. > > > >> See https://git-send-email.io/ (hit next once), they list tools that > >> supposedly work with free accounts too, that could be an option before > >> going the paid route. > > > > Thank you for your clarification. But these choices are a little unethical. > > I've been wrestling with this point for a long time. If a patch is sent via > > a Wi-Fi hacked by the sender, could it be accepted? Then re-consider this > > problem with email -- can the community accept a patch while the sender > > violating the ToS of the email service? I can swallow the reproach of > > conscience, but can community accept? I don't know. But refer to the > > contribution history, this behavior seems acceptable, so I have nothing to > > hesitate about. > > > > I don't think we care if you break the ToS or if you are sending patches > from a WiFi network that you hacked into. I don't know whether those > tools are against the ToS of ProtonMail but it was not my intention to > encourage you to break their ToS. > > > By the way, sorry for my latency of reply. I am a little busy these days. > > And I have to think the problem above so that I can't start writitng this > > email. Luckily, the r28s' commits is not in the devicetree-rebasing now, so > > this delay not cause excessive damage. Once the commits in the > > devicetree-rebasing, I will send the patch as soon as possible. > > > > There's no expectation on how fast you should answer mails so really no > worries. Not having a device supported upstream is also not causing > damage, so really, do not worry, take the time you need or want to take. > > Cheers, > Quentin > I forgot to add receiver and CC. No further comments from my side, just bringing this back on list. Careless, Rong An
