From: Tom Rini via U-Boot <u-boot@lists.u-boot-project.org>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: u-boot@lists.denx.de, u-boot-board-maintainers@lists.denx.de,
u-boot-custodians@lists.denx.de, u-boot@lists.u-boot-project.org
Subject: Re: [ANN] Mailing list migration to lists.u-boot-project.org
Date: Tue, 21 Jul 2026 09:05:28 -0600 [thread overview]
Message-ID: <20260721150528.GV749385@bill-the-cat> (raw)
In-Reply-To: <868f95a2-269b-4879-ad65-b7dbaf2b1b14@cherry.de>
[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]
On Tue, Jul 21, 2026 at 04:52:17PM +0200, Quentin Schulz wrote:
> Hi Tom,
>
> On 7/15/26 7:31 PM, Tom Rini wrote:
> > Hey all,
> >
> > As I've mentioned in previous release emails, we'll be migrating our
> > lists over to lists.u-boot-project.org. The news now is that we have a
> > date. This coming Monday the 20th of July, we'll be turning off the
> > receiving side of lists.denx.de and then importing everything over to
> > lists.u-boot-project.org.
> >
> > What do you need to do? Nothing much. All active subscribers and their
> > preferences will be moved. This includes how lore and patchwork are
> > linked, so all of that will work. We are going to try and ensure no new
> > emails get lost in the migration.
> >
>
> OK but does that mean that whatever mail sent to the old mailing list won't
> make it to the new one once that cut off date is met (that is, yesterday...
> yes I'm really asking at the perfect time :) ). Essentially my question is:
> will we lose mails if they are *now* sent to the old mailing list. I'm
> assuming at some point in the future they will be? Is there a cut-off date
> for that?
The good news is that we were able to setup forwarding correctly, so
there's nothing being lost at the moment. A final date is something we
need to talk about off-list with the people that have access to denx.de
infrastructure still.
Nothing is being missed in *our* archives.
> > Based on feedback from the test migration, we believe we know what was
> > missing to ensure that the archive links are stable, and so that should
> > be the case when we go live again.
> >
>
> I think we're missing an update to lore.kernel.org to monitor the new
> mailing list now? b4 shazam doesn't pick the trailers reviewers provide on
> the mailing list since that date unfortunately (due to the mails not
> appearing on lore.kernel.org I'm assuming).
Yes. I've been trying to reach out to helpdesk@kernel.org for a while
and not had luck, unfortunately.
> I **think** there may be an issue with patchwork as well since I don't see
> my answers in there either, see https://patchwork.ozlabs.org/project/uboot/patch/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/, https://lore.kernel.org/u-boot/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/T/#u
> and https://lists.u-boot-project.org/pipermail/u-boot/2026-July/625465.html
> for an example.
We also had a small window where patchwork wasn't updated (and I'm
talking with Jeremy to backfill that).
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-21 15:05 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
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 [this message]
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=20260721150528.GV749385@bill-the-cat \
--to=u-boot@lists.u-boot-project.org \
--cc=quentin.schulz@cherry.de \
--cc=trini@konsulko.com \
--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.