From: Paul Burton <paul.burton@mips.com>
To: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [RFC] Migration from linux-mips.org to kernel.org
Date: Sat, 1 Dec 2018 06:16:50 +0000 [thread overview]
Message-ID: <20181201061648.bj2kumoefkxcd6z2@pburton-laptop> (raw)
In-Reply-To: <20181128194206.yhdp6247xobkj5cu@pburton-laptop>
Hello all,
On Wed, Nov 28, 2018 at 07:42:07PM +0000, Paul Burton wrote:
> 2) patchwork.linux-mips.org could easily be replaced by any other
> patchwork installation, and kernel.org has one.
>
> 3) The mailing list(s) are what I see as the biggest pain point, but
> we could migrate towards kernel.org infrastructure for this too.
> This may require me to monitor two lists for a while, but that's
> fine.
>
>%
>
> So I'm considering asking for a linux-mips mailing list to be set up at
> kernel.org, with content from linux-mips@linux-mips.org archived on
> lore.kernel.org. MAINTAINERS would be updated to reference the new list,
> and I'd monitor both lists for a while until submissions to the old one
> taper off.
>
> None of this would mean linux-mips.org will go away - I have no control
> over that. It would simply mean that kernel development is no longer
> reliant upon it, instead being based around the kernel.org
> infrastructure which is well maintained and not our problem.
>
> Before I ask for the new mailing list to be set up, I'm asking here
> whether anyone has thoughts or objections?
This is now done - please start using linux-mips@vger.kernel.org instead
of linux-mips@linux-mips.org. The MAINTAINERS file has been updated to
reflect this, so anyone using get_maintainers.pl should start to see the
new list once they update to a new enough kernel.
The list is being archived at https://lore.kernel.org/linux-mips/ - this
contains the history of the @linux-mips.org list, and new mail from the
@vger.kernel.org list going forwards.
Patchwork is available at https://patchwork.kernel.org/project/linux-mips/
As I said before, I'm still subscribed to linux-mips@linux-mips.org &
I'll keep an eye on it for a while, so if you already sent a patch there
please don't feel any need to resend it to the new list - just use the
new list next time.
Thanks,
Paul
prev parent reply other threads:[~2018-12-01 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 19:42 [RFC] Migration from linux-mips.org to kernel.org Paul Burton
2018-12-01 6:16 ` Paul Burton [this message]
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=20181201061648.bj2kumoefkxcd6z2@pburton-laptop \
--to=paul.burton@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-mips@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).