From: Jani Nikula <jani.nikula@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: pr-tracker-bot for drm subsystem?
Date: Mon, 23 Jan 2023 15:13:33 +0200 [thread overview]
Message-ID: <871qnl8kci.fsf@intel.com> (raw)
In-Reply-To: <20230120151024.nflfvgl55wfl6ppj@meerkat.local>
On Fri, 20 Jan 2023, Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Fri, Jan 20, 2023 at 09:09:18AM +0200, Jani Nikula wrote:
>>
>> Konstantin?
>
> Sorry, I didn't mean to scholz you around.
This reply alone was worth the wait. ;D
> The pr-tracker-bot is very much a
> bespoke solution for Linus, so adapting it to other subsystems is not very
> trivial, which is why I've been sitting on this request without any movement.
>
> The code for the bot is available here:
> https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/pr-tracker-bot.py
>
> I can take a look at it in the future, but at the moment I'm still not able to
> work on it, sorry. :(
I guess the question still stands: Regardless of who modifies the
tracker bot and when, do you think you could take on running it for
other subsystems, provided the changes are to your liking, or should the
subsystems adapt it and run their own?
If the latter, there's just not all that much incentive to make it nice,
especially so if you say it's not trivial. It'll just be copy and make
it bespoke for the other subsystem.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-01-23 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 14:06 pr-tracker-bot for drm subsystem? Jani Nikula
2022-10-12 8:30 ` Jani Nikula
2023-01-20 7:09 ` Jani Nikula
2023-01-20 15:10 ` Konstantin Ryabitsev
2023-01-23 13:13 ` Jani Nikula [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=871qnl8kci.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.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).