From: Tom Rini <trini@konsulko.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
u-boot@lists.denx.de, u-boot-board-maintainers@lists.denx.de,
u-boot-custodians@lists.denx.de
Subject: Re: [ANN] Mailing list migration to lists.u-boot-project.org
Date: Wed, 22 Jul 2026 16:01:20 -0600 [thread overview]
Message-ID: <20260722220120.GZ749385@bill-the-cat> (raw)
In-Reply-To: <alpine.DEB.2.21.2607211504130.14485@angie.orcam.me.uk>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
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.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-22 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 17:31 [ANN] Mailing list migration to lists.u-boot-project.org Tom Rini
2026-07-19 18:20 ` Tom Rini
2026-07-20 18:24 ` Mark Kettenis via U-Boot
2026-07-20 22:21 ` Tom Rini via U-Boot
2026-07-21 4:27 ` Maciej W. Rozycki via U-Boot
2026-07-21 13:54 ` Tom Rini via U-Boot
2026-07-21 14:29 ` Maciej W. Rozycki via U-Boot
2026-07-22 22:01 ` Tom Rini [this message]
2026-07-22 22:04 ` Tom Rini
2026-07-21 14:52 ` Quentin Schulz via U-Boot
2026-07-21 15:05 ` Tom Rini via U-Boot
2026-07-21 15:08 ` Quentin Schulz via U-Boot
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=20260722220120.GZ749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=macro@orcam.me.uk \
--cc=mark.kettenis@xs4all.nl \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.