Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

docs: use the lore redirector everywhere

Change all links from using the lkml redirector to the lore redirector,
as the kernel.org admin recently indicated: we shouldn't be using
lkml.kernel.org anymore because the domain can create confusion, as it
indicates it is only valid for messages sent to the LKML; the convention
has been to use https://lore.kernel.org/r/msgid for this reason.

In this process also change three links from using http to https.

Link: https://lore.kernel.org/r/20211006170025.qw3glxvocczfuhar@meerkat.local
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Ingo Molnar <mingo@redhat.com>
CC: Borislav Petkov <bp@alien8.de>
CC: Hu Haowen <src.res@email.cn>
CC: Alex Shi <alexs@kernel.org>
CC: Federico Vaga <federico.vaga@vaga.pv.it>
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
Reviewed-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Link: https://lore.kernel.org/r/5bb55bac6ba10fafab19bf2b21572dd0e2f8cea2.1633593385.git.linux@leemhuis.info
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

Thorsten Leemhuis and committed by
Jonathan Corbet
a9d85efb b0b719ce

+18 -18
+1 -1
Documentation/asm-annotations.rst
··· 64 64 of importing all the crappy, historic, essentially randomly chosen 65 65 debug symbol macro names from the binutils and older kernels? 66 66 67 - .. _discussion: https://lkml.kernel.org/r/20170217104757.28588-1-jslaby@suse.cz 67 + .. _discussion: https://lore.kernel.org/r/20170217104757.28588-1-jslaby@suse.cz 68 68 69 69 Macros Description 70 70 ------------------
+1 -1
Documentation/kbuild/Kconfig.recursion-issue-02
··· 42 42 # "select FW_LOADER" [0], in the end the simple alternative solution to this 43 43 # problem consisted on matching semantics with newly introduced features. 44 44 # 45 - # [0] https://lkml.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com 45 + # [0] https://lore.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com 46 46 47 47 mainmenu "Simple example to demo cumulative kconfig recursive dependency implication" 48 48
+1 -1
Documentation/maintainer/pull-requests.rst
··· 15 15 16 16 Original email thread:: 17 17 18 - http://lkml.kernel.org/r/20171114110500.GA21175@kroah.com 18 + https://lore.kernel.org/r/20171114110500.GA21175@kroah.com 19 19 20 20 21 21 Create Branch
+1 -1
Documentation/networking/msg_zerocopy.rst
··· 50 50 51 51 patchset 52 52 [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY 53 - https://lkml.kernel.org/netdev/20170803202945.70750-1-willemdebruijn.kernel@gmail.com 53 + https://lore.kernel.org/netdev/20170803202945.70750-1-willemdebruijn.kernel@gmail.com 54 54 55 55 56 56 Interface
+2 -2
Documentation/process/maintainer-tip.rst
··· 371 371 - Link: ``https://link/to/information`` 372 372 373 373 For referring to an email on LKML or other kernel mailing lists, 374 - please use the lkml.kernel.org redirector URL:: 374 + please use the lore.kernel.org redirector URL:: 375 375 376 - https://lkml.kernel.org/r/email-message@id 376 + https://lore.kernel.org/r/email-message@id 377 377 378 378 The kernel.org redirector is considered a stable URL, unlike other email 379 379 archives.
+2 -2
Documentation/process/submitting-patches.rst
··· 98 98 99 99 If the patch fixes a logged bug entry, refer to that bug entry by 100 100 number and URL. If the patch follows from a mailing list discussion, 101 - give a URL to the mailing list archive; use the https://lkml.kernel.org/ 101 + give a URL to the mailing list archive; use the https://lore.kernel.org/ 102 102 redirector with a ``Message-Id``, to ensure that the links cannot become 103 103 stale. 104 104 ··· 750 750 best to avoid using In-Reply-To: to link to older versions of the 751 751 series. This way multiple versions of the patch don't become an 752 752 unmanageable forest of references in email clients. If a link is 753 - helpful, you can use the https://lkml.kernel.org/ redirector (e.g., in 753 + helpful, you can use the https://lore.kernel.org/ redirector (e.g., in 754 754 the cover email text) to link to an earlier version of the patch series. 755 755 756 756
+2 -2
Documentation/translations/it_IT/process/submitting-patches.rst
··· 107 107 Se la patch corregge un baco conosciuto, fare riferimento a quel baco inserendo 108 108 il suo numero o il suo URL. Se la patch è la conseguenza di una discussione 109 109 su una lista di discussione, allora fornite l'URL all'archivio di quella 110 - discussione; usate i collegamenti a https://lkml.kernel.org/ con il 110 + discussione; usate i collegamenti a https://lore.kernel.org/ con il 111 111 ``Message-Id``, in questo modo vi assicurerete che il collegamento non diventi 112 112 invalido nel tempo. 113 113 ··· 772 772 sconsigliato l'uso di In-Reply-To: per collegare precedenti versioni. 773 773 In questo modo versioni multiple di una patch non diventeranno un'ingestibile 774 774 giungla di riferimenti all'interno dei programmi di posta. Se un collegamento 775 - è utile, potete usare https://lkml.kernel.org/ per ottenere i collegamenti 775 + è utile, potete usare https://lore.kernel.org/ per ottenere i collegamenti 776 776 ad una versione precedente di una serie di patch (per esempio, potete usarlo 777 777 per l'email introduttiva alla serie). 778 778
+1 -1
Documentation/translations/zh_CN/maintainer/pull-requests.rst
··· 21 21 22 22 原始邮件线程:: 23 23 24 - http://lkml.kernel.org/r/20171114110500.GA21175@kroah.com 24 + https://lore.kernel.org/r/20171114110500.GA21175@kroah.com 25 25 26 26 27 27 创建分支
+2 -2
Documentation/translations/zh_CN/process/submitting-patches.rst
··· 133 133 134 134 如果修补程序修复了一个记录的bug条目,请按编号和URL引用该bug条目。如果补丁来 135 135 自邮件列表讨论,请给出邮件列表存档的URL;使用带有 ``Message-ID`` 的 136 - https://lkml.kernel.org/ 重定向,以确保链接不会过时。 136 + https://lore.kernel.org/ 重定向,以确保链接不会过时。 137 137 138 138 但是,在没有外部资源的情况下,尽量让你的解释可理解。除了提供邮件列表存档或 139 139 bug的URL之外,还要总结需要提交补丁的相关讨论要点。 ··· 599 599 将补丁与以前的相关讨论关联起来,例如,将bug修复程序链接到电子邮件和bug报告。 600 600 但是,对于多补丁系列,最好避免在回复时使用链接到该系列的旧版本。这样, 601 601 补丁的多个版本就不会成为电子邮件客户端中无法管理的引用序列。如果链接有用, 602 - 可以使用 https://lkml.kernel.org/ 重定向器(例如,在封面电子邮件文本中) 602 + 可以使用 https://lore.kernel.org/ 重定向器(例如,在封面电子邮件文本中) 603 603 链接到补丁系列的早期版本。 604 604 605 605 16) 发送git pull请求
+2 -2
Documentation/translations/zh_TW/process/submitting-patches.rst
··· 136 136 137 137 如果修補程序修復了一個記錄的bug條目,請按編號和URL引用該bug條目。如果補丁來 138 138 自郵件列表討論,請給出郵件列表存檔的URL;使用帶有 ``Message-ID`` 的 139 - https://lkml.kernel.org/ 重定向,以確保連結不會過時。 139 + https://lore.kernel.org/ 重定向,以確保連結不會過時。 140 140 141 141 但是,在沒有外部資源的情況下,儘量讓你的解釋可理解。除了提供郵件列表存檔或 142 142 bug的URL之外,還要總結需要提交補丁的相關討論要點。 ··· 602 602 將補丁與以前的相關討論關聯起來,例如,將bug修復程序連結到電子郵件和bug報告。 603 603 但是,對於多補丁系列,最好避免在回復時使用連結到該系列的舊版本。這樣, 604 604 補丁的多個版本就不會成爲電子郵件客戶端中無法管理的引用序列。如果連結有用, 605 - 可以使用 https://lkml.kernel.org/ 重定向器(例如,在封面電子郵件文本中) 605 + 可以使用 https://lore.kernel.org/ 重定向器(例如,在封面電子郵件文本中) 606 606 連結到補丁系列的早期版本。 607 607 608 608 16) 發送git pull請求
+1 -1
Documentation/x86/entry_64.rst
··· 8 8 arch/x86/entry/entry_64.S. A lot of this explanation is adapted from 9 9 an email from Ingo Molnar: 10 10 11 - http://lkml.kernel.org/r/<20110529191055.GC9835%40elte.hu> 11 + https://lore.kernel.org/r/20110529191055.GC9835%40elte.hu 12 12 13 13 The x86 architecture has quite a few different ways to jump into 14 14 kernel code. Most of these entry points are registered in
+2 -2
Documentation/x86/orc-unwinder.rst
··· 177 177 ORC stands for Oops Rewind Capability. 178 178 179 179 180 - .. [1] https://lkml.kernel.org/r/20170602104048.jkkzssljsompjdwy@suse.de 181 - .. [2] https://lkml.kernel.org/r/d2ca5435-6386-29b8-db87-7f227c2b713a@suse.cz 180 + .. [1] https://lore.kernel.org/r/20170602104048.jkkzssljsompjdwy@suse.de 181 + .. [2] https://lore.kernel.org/r/d2ca5435-6386-29b8-db87-7f227c2b713a@suse.cz 182 182 .. [3] http://dustin.wikidot.com/half-orcs-and-orcs