From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: New version of lore available for preview
Date: Wed, 18 Aug 2021 15:07:50 -0400 [thread overview]
Message-ID: <20210818190750.g3xedu7j24sqndo2@nitro.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Hi, all:
We will be deploying a newer version of lore.kernel.org soon, with the
following significant improvements:
1. The default view becomes /all/, which displays messages from all lists and
allows the usual query/retrieval operations across all sources. This
achieves multiple goals, such as ability to aggregate threads regardless on
which list the follow-up discussion took place and will automatically
backfill missing messages if they are present on one list but not on
another.
2. Instead of a single system, lore.kernel.org will be mirrored across three
nodes currently serving git.kernel.org. This both reduces single points of
failure and makes things faster for folks in EU/APAC.
3. The web interface will now respect your browser-preferred color scheme and
will display dark mode interface if that's how you like it.
You can access the new version at https://x-lore.kernel.org/ and it should be
fully usable for daily operations.
You can use x-lore with b4, though I strongly recommend switching to master
branch in order to better deal with some of the changes happening on the
server-side. Simply add the following to your ~/.gitconfig:
[b4]
midmask = https://x-lore.kernel.org/r/%s
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.
Best regards,
-Konstantin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2021-08-18 19:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:07 Konstantin Ryabitsev [this message]
2021-08-18 19:09 ` New version of lore available for preview 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
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=20210818190750.g3xedu7j24sqndo2@nitro.local \
--to=konstantin@linuxfoundation.org \
--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).