Documentation/translations/zh_CN/doc-guide/maintainer-profile.rst
Source file repositories/reference/linux-study-clean/Documentation/translations/zh_CN/doc-guide/maintainer-profile.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/translations/zh_CN/doc-guide/maintainer-profile.rst- Extension
.rst- Size
- 1853 bytes
- Lines
- 44
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
.. SPDX-License-Identifier: GPL-2.0
.. include:: ../disclaimer-zh_CN.rst
:Original: Documentation/doc-guide/maintainer-profile.rst
:译者: 吴想成 Wu XiangCheng <bobwxc@email.cn>
文档子系统维护人员条目概述
==========================
文档“子系统”是内核文档和相关基础设施的中心协调点。它涵盖了 Documentation/ 下
的文件层级(Documentation/devicetree 除外)、scripts/ 下的各种实用程序,并且
在某些情况下的也包括 LICENSES/ 。
不过值得注意的是,这个子系统的边界比通常更加模糊。许多其他子系统维护人员需要
保持对 Documentation/ 某些部分的控制,以便于可以更自由地做更改。除此之外,
许多内核文档都以kernel-doc注释的形式出现在源代码中;这些注释通常(但不总是)
由相关的子系统维护人员维护。
文档子系统的邮件列表是<linux-doc@vger.kernel.org>。
补丁应尽量针对docs-next树。
提交检查单补遗
--------------
在进行文档更改时,您应当构建文档以测试,并确保没有引入新的错误或警告。生成
HTML文档并查看结果将有助于避免对文档渲染结果的不必要争执。
开发周期的关键节点
------------------
补丁可以随时发送,但在合并窗口期间,响应将比通常慢。文档树往往在合并窗口打开
之前关闭得比较晚,因为文档补丁导致回归的风险很小。
审阅节奏
--------
我(译注:指Jonathan Corbet <corbet@lwn.net>)是文档子系统的唯一维护者,我在
自己的时间里完成这项工作,所以对补丁的响应有时会很慢。当补丁被合并时(或当我
决定拒绝合并补丁时),我都会发送通知。如果您在发送补丁后一周内没有收到回复,
请不要犹豫,发送提醒就好。
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.