From: Alex Shi <seakeel@gmail.com>
To: Sanjeev Gupta <ghane0@gmail.com>, linux-doc@vger.kernel.org
Cc: corbet@lwn.net, Alex Shi <alexs@kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Wu XiangCheng <bobwxc@email.cn>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH] Documentation/translations/zh_CN: switch LWN links to https
Date: Tue, 8 Jun 2021 14:25:54 +0800 [thread overview]
Message-ID: <5294d79d-56fc-7d55-6cc9-54a9ff7baa8f@gmail.com> (raw)
In-Reply-To: <19db70b6.AU0AADJwA04AAAAAAAAAAKAiBvEAAAAAAMcAAAAAAA6qeABgvvZE@mailjet.com>
This looks fine. But actually much of links don't work for me.
I am not sure it's a server issue or a region issue.
Thanks
Alex
On 6/8/21 12:17 PM, Sanjeev Gupta wrote:
> -(http://lwn.net/articles/131776/)
> +(https://lwn.net/articles/131776/)
>
> 实际情况却是不同的;与特定模块相比,内核开发人员更关心系统稳定性、长期维护
> 以及找到问题的正确解决方案。这个故事的寓意是把重点放在问题上——而不是具体的
> diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst
> index 94f7f866f103..b277895c6d2d 100644
> --- a/Documentation/translations/zh_CN/process/4.Coding.rst
> +++ b/Documentation/translations/zh_CN/process/4.Coding.rst
> @@ -149,7 +149,7 @@ Linus对这个问题给出了最佳答案:
> 所以我们不会通过引入新问题来修复错误。这种方式是靠不住的,没人知道
> 是否真的有进展。是前进两步、后退一步,还是前进一步、后退两步?
>
> -(http://lwn.net/articles/243460/)
> +(https://lwn.net/articles/243460/)
>
> 特别不受欢迎的一种回归类型是用户空间ABI的任何变化。一旦接口被导出到用户空间,
> 就必须无限期地支持它。这一事实使得用户空间接口的创建特别具有挑战性:因为它们
> diff --git a/Documentation/translations/zh_CN/process/7.AdvancedTopics.rst b/Documentation/translations/zh_CN/process/7.AdvancedTopics.rst
> index 6d0dadae13b1..668f4fe680f0 100644
> --- a/Documentation/translations/zh_CN/process/7.AdvancedTopics.rst
> +++ b/Documentation/translations/zh_CN/process/7.AdvancedTopics.rst
> @@ -98,7 +98,7 @@ Git提供了一些强大的工具,可以让您重写开发历史。一个不
> 你可以给我发补丁,但当我从你那里拉取一个Git补丁时,我需要知道你清楚
> 自己在做什么,我需要能够相信事情而 *无需* 手动检查每个单独的更改。
>
> -(http://lwn.net/articles/224135/)。
> +(https://lwn.net/articles/224135/)。
>
> 为了避免这种情况,请确保给定分支中的所有补丁都与相关主题紧密相关;“驱动程序
> 修复”分支不应更改核心内存管理代码。而且,最重要的是,不要使用Git树来绕过
> diff --git a/Documentation/translations/zh_CN/process/8.Conclusion.rst b/Documentation/translations/zh_CN/process/8.Conclusion.rst
> index 71c3e30efc6f..b0b6cc270aec 100644
> --- a/Documentation/translations/zh_CN/process/8.Conclusion.rst
> +++ b/Documentation/translations/zh_CN/process/8.Conclusion.rst
> @@ -27,7 +27,7 @@
> 不同的网站在各个细节层次上讨论内核开发。本文作者想谦虚地建议用 https://lwn.net/
> 作为来源;有关许多特定内核主题的信息可以通过以下网址的 LWN 内核索引找到:
>
> - http://lwn.net/kernel/index/
> + https://lwn.net/kernel/index/
>
> 除此之外,内核开发人员的一个宝贵资源是:
>
> @@ -38,7 +38,7 @@
> 关于内核开发有很多书:
>
> 《Linux设备驱动程序》第三版(Jonathan Corbet、Alessandro Rubini和Greg Kroah Hartman)
> - 线上版本在 http://lwn.net/kernel/ldd3/
> + 线上版本在 https://lwn.net/kernel/ldd3/
>
> 《Linux内核设计与实现》(Robert Love)
next parent reply other threads:[~2021-06-08 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19db70b6.AU0AADJwA04AAAAAAAAAAKAiBvEAAAAAAMcAAAAAAA6qeABgvvZE@mailjet.com>
2021-06-08 6:25 ` Alex Shi [this message]
[not found] <baeb58d3.AUUAAC5sESEAAAAAAAAAAKAiBvYAAAAAAMcAAAAAAA6qeABgmKYT@mailjet.com>
2021-05-10 4:40 ` [PATCH] Documentation/translations/zh_CN: switch LWN links to https Wu X.C.
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=5294d79d-56fc-7d55-6cc9-54a9ff7baa8f@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=ghane0@gmail.com \
--cc=grandmaster@al2klimov.de \
--cc=linux-doc@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=masahiroy@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).