Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini <trini@konsulko.com>]

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

On Wed, Jul 22, 2026 at 04:01:20PM -0600, Tom Rini wrote:
> On Tue, Jul 21, 2026 at 03:29:23PM +0100, Maciej W. Rozycki wrote:
> > On Tue, 21 Jul 2026, Tom Rini wrote:
> > 
> > > >  That's going to break patch submissions, isn't it?
> > > 
> > > Looks like it's working:
> > > https://patchwork.ozlabs.org/project/uboot/patch/20260721063050.18756-1-dinesh.maniyam@altera.com/
> > 
> >  It breaks for `git am' though, such as for picking up patches directly 
> > from the mailing list via the MUA (hmm, why hasn't this particular patch 
> > arrive here?).  There are other issues with the rewrite, such as the 
> > inability to sort messages by authors in the mailbox, but the former is 
> > possibly the most painful.
> > 
> > > Not my favorite that it's going to have "... via U-Boot" in patchwork
> > > only. And we already have "... via B4 Relay" in others. We aren't the
> > > only project OSU OSL is hosting mailman for, so I'd assume this is a
> > > solved problem.
> > 
> >  Yep, GNU toolchain lists I'm on that are used for patch distribution 
> > (such as <binutils@sourceware,org>, <gcc-patches@gcc.gnu.org>, but not 
> > <gcc-help@gcc.gnu.org>) simply disabled such rewriting, after numerous 
> > discussions (not sure what OSU OSL is though).
> > 
> >  Up to you to decide, I just wanted to share my concern.
> 
> So, thank you both, Maciej and Mark for bringing this up. I relayed this
> back to OSU OSL again and it was indeed really a misconfiguration on the
> migration and not a policy that we had to keep. It's now been fixed.

... in the case of domains (most of them, but *not* xs4all.nl) which
don't enforce DMARC but instead either aren't strict (most) or are
quarantine (kernel.org for example).

-- 
Tom

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