On Fri, 20 Jan 2023, Konstantin Ryabitsev
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
On Fri, Jan 20, 2023 at 09:09:18AM +0200, Jani Nikula wrote:
>
> Konstantin?
Sorry, I didn't mean to scholz you around. 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
Konstantin?
On Thu, 15 Sep 2022, Jani Nikula wrote:
> Hey all, I'd be interested in having the pr-tracker-bot [1] set up for
> the drm subsystem, following the dri-devel mailing list [2] and
> notifying when the pull requests have been merged to either the drm-next
> or drm-fixes branches of
Ping?
On Thu, 15 Sep 2022, Jani Nikula wrote:
> Hey all, I'd be interested in having the pr-tracker-bot [1] set up for
> the drm subsystem, following the dri-devel mailing list [2] and
> notifying when the pull requests have been merged to either the drm-next
> or drm-fixes branches of the
Hey all, I'd be interested in having the pr-tracker-bot [1] set up for
the drm subsystem, following the dri-devel mailing list [2] and
notifying when the pull requests have been merged to either the drm-next
or drm-fixes branches of the main drm repository [3].
What would this require in terms
