All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>,
	Cyril Hrubis <chrubis@suse.cz>,
	ltp@lists.linux.it, Jan Stancek <jstancek@redhat.com>,
	Andrea Cervesato <andrea.cervesato@suse.de>,
	Avinesh Kumar <akumar@suse.de>, Martin Doucha <mdoucha@suse.cz>,
	Wei Gao <wegao@suse.com>
Subject: Re: [LTP] [PATCH 1/1] Switch to patchwork.kernel.org
Date: Mon, 3 Aug 2026 12:24:07 +0200	[thread overview]
Message-ID: <20260803102407.GB217746@pevik> (raw)
In-Reply-To: <anBi9ybOfNzbxALE@linux.dev>

Hi Li, all,

> Andrea Cervesato wrote:

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

> > that looks like a really long period of time. lore.kernel.org/ltp/
> > is not enough?

> I guess Cyril means to look back the history of patch discussion when needed.

Well, for the patch history we have LTP ML archive [1] and lore (has longer
history than patchwork [2]). Although patch view in patchwork might be easier to
read.

I meant something different: people have probably sent LTP patchwork ozlabs
instance links to other, put in bugzilla etc. Patchwork use Message-id, therefore
patch link [3] can be easily converted to lore [4]. Patch comment [5] don't.
That's why I'd keep abandoned LTP instance for some time, but maybe we just don't care.
Obviously keeping it around depends on ozlabs maintainers decision.

> Or, can we tar the mail discussion for recent years and store it somewhere?

FYI we already have history in git as an public-inbox [6]:
git clone https://lore.kernel.org/ltp/

> Anyway, for the patch:

> Reviewed-by: Li Wang <li.wang@linux.dev>

Thanks!

Kind regards,
Petr

[1] https://lists.linux.it/pipermail/ltp/
[2] https://lore.kernel.org/ltp/?t=20180216133201
[3] https://patchwork.ozlabs.org/project/ltp/patch/20260731054548.133241-1-pvorel@suse.cz/
[4] https://lore.kernel.org/ltp/20260731054548.133241-1-pvorel@suse.cz/
[5] https://patchwork.ozlabs.org/comment/3731798/
[6] https://lore.kernel.org/ltp/_/text/mirror/

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

  reply	other threads:[~2026-08-03 10:33 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 [this message]
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
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=20260803102407.GB217746@pevik \
    --to=pvorel@suse.cz \
    --cc=akumar@suse.de \
    --cc=andrea.cervesato@suse.com \
    --cc=andrea.cervesato@suse.de \
    --cc=chrubis@suse.cz \
    --cc=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    --cc=wegao@suse.com \
    /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.