From: Peter Korsgaard <peter@korsgaard.com>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: buildroot@busybox.net, Stephen Rothwell <sfr@canb.auug.org.au>,
Joel Stanley <joel@jms.id.au>
Subject: Re: [Buildroot] What's wrong with patchwork
Date: Fri, 03 Sep 2021 08:46:23 +0200 [thread overview]
Message-ID: <877dfyrwao.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <690b56e57bebb7a4730273ad3f958d6c23e68680.camel@ozlabs.org> (Jeremy Kerr's message of "Fri, 03 Sep 2021 11:01:57 +0800")
>>>>> "Jeremy" == Jeremy Kerr <jk@ozlabs.org> writes:
Hi,
>> I just noticed that my buildroot list filter is no longer working.
>> The listid used to be:
>>
>> List-Id: Discussion and development of buildroot
>> <buildroot.busybox.net>
>>
>> but now it is set to:
>>
>> List-Id: Discussion and development of buildroot
>> <buildroot.lists.buildroot.org>
>>
>> It looks like buildroot list changed domains recently. Perhaps the
>> subscription for incoming-buildroot@ didn't get moved over to the new
>> setup?
> Ah, that'd explain missing patches then (assuming delivery is
> working...). Patchwork relies on the list ID to correlate mail to
> projects. Since it doesn't know about the new list-id, it'll be
> dropping those.
> I'll update the list-id for the buildroot patchwork project.
Sorry about this. The mailing list setup had a number of annoying issues
(the busybox.net vs buildroot.org, how uclibc/busybox lists were also
shown, TLS certificate not matching the hostname, ..) so we recently
worked with the OSUOSL guys to fix it.
We've had some teething issues, but I believe it is working now, if not
let me know.
With the changes, the list page
(https://lists.buildroot.org/mailman/listinfo) now has correct TLS
config and only shows the buildroot list and the List-id is
buildroot.lists.buildroot.org.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-03 6:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YS/GToWU8Wx8XOR6@pevik>
[not found] ` <CACPK8XcMS1nW446xL--CLShQTZA0opSNE4Yr_cnY1Ayh3vYe=A@mail.gmail.com>
[not found] ` <20210903092217.7f02055a@canb.auug.org.au>
2021-09-03 0:40 ` [Buildroot] What's wrong with patchwork Jeremy Kerr
[not found] ` <20210903105610.790366ac@canb.auug.org.au>
2021-09-03 2:58 ` Joel Stanley
2021-09-03 3:01 ` Jeremy Kerr
2021-09-03 6:46 ` Peter Korsgaard [this message]
2021-09-03 6:49 ` Jeremy Kerr
2021-09-03 10:21 ` Giulio Benetti
2021-09-03 12:00 ` Peter Korsgaard
2021-09-03 16:49 ` Giulio Benetti
2021-09-03 19:38 ` Nevo Hed
2021-09-03 19:58 ` Giulio Benetti
2021-09-04 9:37 ` Peter Korsgaard
2021-09-27 2:31 ` Joel Stanley
2021-09-28 2:34 ` Jeremy Kerr
2021-09-28 5:21 ` Yann E. MORIN
2021-09-28 5:30 ` Jeremy Kerr
2021-09-28 5:39 ` Yann E. MORIN
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=877dfyrwao.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=sfr@canb.auug.org.au \
/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.