From: Slade Watkins <srw@sladewatkins.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: drm next for 6.3-rc1
Date: Fri, 24 Feb 2023 20:49:03 -0500 [thread overview]
Message-ID: <CA+pv=HMOXiftTEcSLeTnQLxdxxD+GushtCwO197icDYm=kPwMw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wj4ShzDcZVx07ObELz06dL7m3Ax-p014rAmxGQ3D0brXA@mail.gmail.com>
On Fri, Feb 24, 2023 at 8:35 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> If you were waiting for a pr-tracker-bot reply, I think you need to
> put "{GIT PULL]" in the subject line for the automation to trigger on
> it.
Had to double check, but yes, that's exactly it:
PULL_SUBJECT_RE = [
re.compile(r'^\S*:?\s*\[GIT', re.IGNORECASE),
re.compile(r'^\S*:?\s*\[PULL', re.IGNORECASE),
re.compile(r'^\S*:?\s*\[PLEASE PULL', re.IGNORECASE),
]
Link: https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/pr-tracker-bot.py
-- Slade
WARNING: multiple messages have this Message-ID (diff)
From: Slade Watkins <srw@sladewatkins.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm next for 6.3-rc1
Date: Fri, 24 Feb 2023 20:49:03 -0500 [thread overview]
Message-ID: <CA+pv=HMOXiftTEcSLeTnQLxdxxD+GushtCwO197icDYm=kPwMw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wj4ShzDcZVx07ObELz06dL7m3Ax-p014rAmxGQ3D0brXA@mail.gmail.com>
On Fri, Feb 24, 2023 at 8:35 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> If you were waiting for a pr-tracker-bot reply, I think you need to
> put "{GIT PULL]" in the subject line for the automation to trigger on
> it.
Had to double check, but yes, that's exactly it:
PULL_SUBJECT_RE = [
re.compile(r'^\S*:?\s*\[GIT', re.IGNORECASE),
re.compile(r'^\S*:?\s*\[PULL', re.IGNORECASE),
re.compile(r'^\S*:?\s*\[PLEASE PULL', re.IGNORECASE),
]
Link: https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/pr-tracker-bot.py
-- Slade
next prev parent reply other threads:[~2023-02-25 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 0:10 drm next for 6.3-rc1 Dave Airlie
2023-02-23 0:10 ` Dave Airlie
2023-02-25 1:29 ` Dave Airlie
2023-02-25 1:29 ` Dave Airlie
2023-02-25 1:35 ` Linus Torvalds
2023-02-25 1:35 ` Linus Torvalds
2023-02-25 1:49 ` Slade Watkins [this message]
2023-02-25 1:49 ` Slade Watkins
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='CA+pv=HMOXiftTEcSLeTnQLxdxxD+GushtCwO197icDYm=kPwMw@mail.gmail.com' \
--to=srw@sladewatkins.net \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.