All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] Switch to patchwork.kernel.org
Date: Mon, 3 Aug 2026 12:33:35 +0200	[thread overview]
Message-ID: <20260803103335.GD217746@pevik> (raw)
In-Reply-To: <anBdxCKHlpedf2rf@yuki.lan>

Hi Cyril, all,

> Hi!
> > since we have all active LTP maintainers enabled as patchwork maintainers in the
> > kernel.org instance [1] I'd like in few hours merge this patch to finally move
> > to patchwork.kernel.org. FYI we already have 18 patches on it, AI review is
> > there as well.

> > @Cyril @Li @Jan: Could you please ack this patch?

> Acked-by: Cyril Hrubis <chrubis@suse.cz>

Thank you!

> Btw, we may want to add the patchwork link into kernel MINTAINTERS file, 

Very good point, thanks! I'll send a patch adding a new one once we switch.

> > I wonder when to stop receiving patches on the old ozlabs instance [2] We should
> > probably ask for it soon so that people don't think we stop maintaining it.

> Sounds about right.

> > I hoped that the last patch on that instance would be "Switch to
> > patchwork.kernel.org" [3], but there are new patches now. OTOH we then no longer
> > get updates for the old patchsets (there are 54 patches which aren't on the new
> > kernel.org instance + already 6 duplicates).

> > Other question is when to ask about for removing the old instance. I'd keep it
> > at least for some time (can be useful + there might be bookmarks, instance has
> > 13079 patches, first one in 2018-02-28). WDYT?

> I would keep it around at least for a year or two, I sometimes look up
> old patches there.

+1

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2026-08-03 10:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  5:45 [LTP] [PATCH 1/1] Switch to patchwork.kernel.org Petr Vorel
2026-07-31  6:14 ` [LTP] " linuxtestproject.agent
2026-07-31  7:25 ` [LTP] [PATCH 1/1] " Avinesh Kumar via ltp
2026-07-31  7:43 ` Andrea Cervesato via ltp
2026-08-03  9:13   ` Petr Vorel
2026-08-03  9:22     ` Cyril Hrubis
2026-08-03  9:28       ` Andrea Cervesato via ltp
2026-08-03  9:44         ` Li Wang
2026-08-03 10:24           ` Petr Vorel
2026-08-03 10:34             ` Andrea Cervesato via ltp
2026-08-03 11:06               ` Petr Vorel
2026-08-03 10:24         ` Cyril Hrubis
2026-08-03 10:26           ` Petr Vorel
2026-08-03 10:33       ` Petr Vorel [this message]
2026-08-03  9:23     ` Andrea Cervesato via ltp
2026-08-03  9:44       ` Petr Vorel
2026-08-03 10:14         ` Andrea Cervesato via ltp
2026-08-03  9:29     ` Jan Stancek via ltp

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=20260803103335.GD217746@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.