tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: New version of lore available for preview
Date: Thu, 2 Sep 2021 16:14:02 -0400	[thread overview]
Message-ID: <20210902201402.bbdttirbb5ckrtiz@meerkat.local> (raw)
In-Reply-To: <20210902195332.GA2493828@nvidia.com>

On Thu, Sep 02, 2021 at 04:53:32PM -0300, Jason Gunthorpe wrote:
> > Please report any problems or hiccups that you discover. There is no specific
> > ETA for the new version go-live, but if all goes well, the hope is to have it
> > in place by end of August.
> 
> Hi Konstantin,
> 
> The https://lore.kernel.org/lists.txt URL now gives a 404, is this
> expected?
> 
> If so does someone have a fix for lorifier.py? It is very unhappy to lose
> this URL..

I forgot about the lorifier. However, the upside is that you don't really need
the lists.txt URL any more, as you can just blanket aim things at
lore.kernel.org/all/<message-id> -- if it's on lore, it will be there.

I pushed a quick fix here:
https://github.com/mricon/lorifier/

If you really want to only show the link if a message is actually on lore,
it's easy to add a HEAD call to see if we get a 404 or not, so let me know if
it's something you'd need.

-K

  reply	other threads:[~2021-09-02 20:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 19:07 New version of lore available for preview Konstantin Ryabitsev
2021-08-18 19:09 ` Jason A. Donenfeld
2021-08-18 19:48   ` Konstantin Ryabitsev
2021-08-18 19:50     ` Junio C Hamano
2021-08-25 16:30 ` Rob Herring
2021-08-25 16:44   ` Konstantin Ryabitsev
2021-08-25 21:39     ` Josh Triplett
2021-08-26 14:04       ` Konstantin Ryabitsev
2021-08-26 23:04         ` Josh Triplett
2021-09-02 19:53 ` Jason Gunthorpe
2021-09-02 20:14   ` Konstantin Ryabitsev [this message]
2021-09-02 22:44     ` Masahiro Yamada
2021-09-03 10:30       ` Mark Brown
2021-09-03 15:21       ` Konstantin Ryabitsev
2021-09-06  9:59         ` Lee Jones
2021-09-08 18:37           ` Konstantin Ryabitsev
2021-09-09 12:49             ` Steven Rostedt
2021-09-09 13:32               ` Lee Jones
2021-09-09 13:38                 ` Konstantin Ryabitsev
2021-09-09 13:45                   ` Lee Jones
2021-09-09 14:39                     ` Konstantin Ryabitsev
2021-09-09 15:24                       ` James Bottomley
2021-09-09 16:17                         ` Konstantin Ryabitsev
2021-09-09 14:51                     ` Alexandre Belloni
2021-09-09 15:00                       ` Konstantin Ryabitsev
2021-09-09 13:43                 ` Greg KH
2021-09-09 13:54                   ` Lee Jones
2021-09-09 13:56                     ` Mark Brown
2021-09-09 14:05                       ` Lee Jones
2021-09-10 16:07                   ` Bjorn Andersson
2021-09-10 16:12                     ` Mark Brown
2021-09-10 17:21                       ` Peter Zijlstra
2021-09-09 13:55                 ` Steven Rostedt
2021-09-09 14:04                   ` Lee Jones
2021-09-09 14:51                 ` Peter Zijlstra
2021-09-10  6:10                   ` Lee Jones
2021-09-02 23:38     ` Jason Gunthorpe

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=20210902201402.bbdttirbb5ckrtiz@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=jgg@nvidia.com \
    --cc=tools@linux.kernel.org \
    --cc=users@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 NNTP newsgroup(s).