From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Joseph Myers <josmyers@redhat.com>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Re: Hashing out the scope of work
Date: Tue, 30 Apr 2024 08:41:44 -0400 [thread overview]
Message-ID: <6bcada32-c63f-4906-9fea-3daf53966b03@gotplt.org> (raw)
In-Reply-To: <20240430-polar-jaguar-of-debate-04ddba@lemur>
On 2024-04-30 08:30, Konstantin Ryabitsev wrote:
>> I think it's the details of what patches / patch series still need
>> review that's the most valuable part to preserve and migrate.
>
> I think we can accomplish this without having to touch the DB. We can
> identify the patches that are still open and replay them from the
> mailing list into the new system. This would be a lot simpler than doing
> database surgery.
That would also allow the trybots to run a second time, flagging patches
that no longer apply. It'll be a decent way to weed out outdated
patches too.
thanks,
Sid
next prev parent reply other threads:[~2024-04-30 12:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 16:45 Hashing out the scope of work Konstantin Ryabitsev
2024-04-24 21:15 ` Ian Kelling
2024-04-25 1:31 ` Konstantin Ryabitsev
2024-04-25 20:06 ` Ian Kelling
2024-04-26 16:06 ` Siddhesh Poyarekar
2024-05-13 17:28 ` Carlos O'Donell
2024-04-29 14:09 ` Joseph Myers
2024-04-29 15:23 ` Konstantin Ryabitsev
2024-04-29 16:35 ` Joseph Myers
2024-04-29 18:52 ` Siddhesh Poyarekar
2024-04-29 20:47 ` Joseph Myers
2024-04-29 21:01 ` Konstantin Ryabitsev
2024-04-29 21:58 ` Joseph Myers
2024-04-30 12:30 ` Konstantin Ryabitsev
2024-04-30 12:41 ` Siddhesh Poyarekar [this message]
2024-05-02 19:27 ` Joseph Myers
2024-05-07 20:36 ` Konstantin Ryabitsev
2024-05-07 21:45 ` Joseph Myers
2024-05-13 16:31 ` Carlos O'Donell
2024-05-17 21:22 ` Carlos O'Donell
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=6bcada32-c63f-4906-9fea-3daf53966b03@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=josmyers@redhat.com \
--cc=konstantin@linuxfoundation.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).