From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-hotplug@vger.kernel.org
Subject: Re: PSA: migrating linux-hotplug to new vger infrastructure
Date: Mon, 6 Nov 2023 17:35:16 +0100 [thread overview]
Message-ID: <2023110602-creasing-swell-b5c2@gregkh> (raw)
In-Reply-To: <20231106-tough-zebra-of-potency-a8b32b@nitro>
On Mon, Nov 06, 2023 at 09:29:47AM -0500, Konstantin Ryabitsev wrote:
> On Mon, Nov 06, 2023 at 02:33:22PM +0100, Greg KH wrote:
> > > I plan to migrate the linux-hotplug@vger.kernel.org list to the new
> > > infrastructure this week. We're still doing it list-by-list to make sure that
> > > we don't run into scaling issues with the new infra.
> > >
> > > The migration will be performed live and should not require any downtime.
> > > There will be no changes to how anyone interacts with the list after
> > > migration is completed, so no action is required on anyone's part.
> > >
> > > Please let me know if you have any concerns.
> >
> > I think the list can just be deleted, there's no traffic anymore, and
> > "hotplug" doesn't make any sense anymore as "everything" can be
> > added/removed from a Linux system these days.
> >
> > So can we just remove it?
>
> There seems to be legitimate traffic from last year, so I would lean towards
> migrating it for now and revisiting the question of sunsetting it next year,
> after the dust settles a bit.
Ok, fair enough, trying to make it easier :)
next prev parent reply other threads:[~2023-11-06 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 13:21 PSA: migrating linux-hotplug to new vger infrastructure Konstantin Ryabitsev
2023-11-06 13:33 ` Greg KH
2023-11-06 14:29 ` Konstantin Ryabitsev
2023-11-06 16:35 ` Greg KH [this message]
2023-11-06 19:05 ` Eric Pilmore
2023-11-06 19:25 ` Greg KH
2023-11-06 20:46 ` Matthew Dharm
2023-11-07 5:12 ` Eric Pilmore
2023-11-07 6:00 ` Greg KH
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=2023110602-creasing-swell-b5c2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-hotplug@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 read-only IMAP folder(s) and NNTP newsgroup(s).