Re: [PATCH v3 5/6] docs/zh_CN: doc-guide: document macOS Sphinx setup

Weijie Yuan <[email protected]>
Newsgroups org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Fri, Aug 14, 2026 at 12:04:26AM +0800, Chen Miao wrote:
> Weijie Yuan <[email protected]> 于2026年8月13日周四 23:36写道:
> >
> > On Thu, Aug 13, 2026 at 02:23:22AM +0800, Chen Miao wrote:
> > > Translate the macOS Sphinx dependency setup added to the English
> > > documentation. Keep the translation in a separate patch so translation
> > > status tooling can track the source change correctly.
> > >
> > > Signed-off-by: Chen Miao <[email protected]>
> >
> > Acked-by: Weijie Yuan <[email protected]>
> >
> > > ---
> > >  .../translations/zh_CN/doc-guide/sphinx.rst     | 17 ++++++++++++++++-
> > >  1 file changed, 16 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/translations/zh_CN/doc-guide/sphinx.rst b/Documentation/translations/zh_CN/doc-guide/sphinx.rst
> > > index 3375c6f3a..e6d42d970 100644
> > > --- a/Documentation/translations/zh_CN/doc-guide/sphinx.rst
> > > +++ b/Documentation/translations/zh_CN/doc-guide/sphinx.rst
> > > @@ -110,6 +110,22 @@ PDF和LaTeX构建
> > >
> > >       使用Sphinx的系统打包,而不是Python虚拟环境。
> > >
> > > +macOS 默认使用不区分文件名大小写的 APFS 卷,而内核源码树中存在仅大小写
> > > +不同的文件。克隆源码前,请用 ``diskutil apfs list`` 找到 APFS 容器标识符,
> > > +将下面的 ``diskX`` 替换为该标识符,并创建一个额外的大小写敏感卷::
> > > +
> > > +     diskutil apfs addVolume diskX APFSX Linux
> >
> > This CLI way definitely works, while the Disk Utility app also provides
> > an easy way to do this. ;-) Shall we add more description or tips about
> > it? But I'm also satisfied with the current situation, as some hackers
> > who would read this may prefer CLI way.
> >
> I don't think GUI instructions are necessary here. Readers who find diskutil
> unfamiliar can easily search for the equivalent steps in Disk Utility. The same
> operation can also be performed using Disk Utility.

Yeah, agreed. Thanks.
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.