From: Mike Rapoport <rppt@kernel.org>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: Dan Rue <danrue@gmail.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
tools@kernel.org
Subject: Re: [PATCH] add sashiko URLs
Date: Fri, 17 Apr 2026 10:38:20 +0300 [thread overview]
Message-ID: <aeHjbOXjWWzFnAuV@kernel.org> (raw)
In-Reply-To: <20260417-original-smooth-heron-96be80@sudeepholla>
On Fri, Apr 17, 2026 at 07:50:09AM +0100, Sudeep Holla wrote:
> On Thu, Apr 16, 2026 at 02:21:56PM +0300, Mike Rapoport wrote:
> > sashiko is gaining traction and it's easy to add its URLs along with
> > lore ones.
> >
> > Signed-off-by: Mike Rapoport <rppt@kernel.org>
> > ---
> > lorifier.py | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/lorifier.py b/lorifier.py
> > index be7294b..96529bd 100755
> > --- a/lorifier.py
> > +++ b/lorifier.py
> > @@ -25,6 +25,7 @@ import sys
> > from email.utils import mktime_tz, parsedate_tz, formatdate
> >
> > LORE_MASK = "https://lore.kernel.org/all/%s"
> > +SASHIKO_MASK = "https://sashiko.dev/#/message/%s"
>
> Just curious on the choice of
> "https://sashiko.dev/#/message/%s"
> over
> "https://sashiko.dev/#/patchset/%s"
>
> As the latter points to former while the reverse is not true unless I am
> missing something.
Patchset URL does not include message id, e.g:
https://sashiko.dev/#/patchset/20260417223004.1-evm-xattrs-v2-pengpeng%40iscas.ac.cn
I talked to Roman and he said he'll add links to patchsets from messages
Really Soon.
> --
> Regards,
> Sudeep
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-04-17 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 11:21 [PATCH] add sashiko URLs Mike Rapoport
2026-04-16 19:17 ` Kees Cook
2026-04-16 19:26 ` Konstantin Ryabitsev
2026-04-17 6:50 ` Sudeep Holla
2026-04-17 7:38 ` Mike Rapoport [this message]
2026-04-17 8:28 ` Sudeep Holla
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=aeHjbOXjWWzFnAuV@kernel.org \
--to=rppt@kernel.org \
--cc=danrue@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=sudeep.holla@kernel.org \
--cc=tools@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