Re: [PATCH] add sashiko URLs

Sudeep Holla <[email protected]>
Newsgroups org.kernel.linux.tools
Message-ID <20260417-umber-oxpecker-of-brotherhood-3a26cc@sudeepholla>
On Fri, Apr 17, 2026 at 10:38:20AM +0300, Mike Rapoport wrote:
> 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 <[email protected]>
> > > ---
> > >  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

Yes it does not directly specify message id, but it does presents links to it.

For example, above patchset link has links to these:

https://sashiko.dev/#/message/20260407153002.2-evm-xattrs-pengpeng%40iscas.ac.cn
https://sashiko.dev/#/message/d95993e3d879bec4c9e3416906d409cca9c8ffeb.camel%40huaweicloud.com
https://sashiko.dev/#/message/20260417190004.4-evm-xattrs-reply-pengpeng%40iscas.ac.cn
https://sashiko.dev/#/message/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.
>  

Cool, that would be great.

-- 
Regards,
Sudeep
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.