今日重点：✍️ 写作——内核社区大量协作靠邮件往来，而会议纪要是其中最容易被写坏的一种： 写完只有参会的人看得懂，没去的人还是一头雾水。今天拆 Pasha Tatashin 的 Hypervisor Live Update 纪要—— 这份写得好在哪，有什么可以直接抄的结构。
📖 原文节选（真实邮件，逐字引用）
/ sectionHi everybody, Here are the notes from our Hypervisor Live Update call held on September 21. These notes are intended to bring those who could not attend up to speed and to keep the momentum going between meetings.
出处：Pasha Tatashin，[Hypervisor Live Update] Notes from September 21, 2026， linux-mm，09-25 22:30 北京。 原文
✍️ 拆解：让纪要可交接的四条规矩
/ column 开头先交代「写给谁、解决什么」 These notes are intended to bring those who could not attend up to speed and to keep the momentum going between meetings. intended to 说明用途；bring ... up to speed（让……跟上进度）是固定说法。两个目的讲得很清楚：给缺席的人补课、在两次会议之间保持推进。写纪要别直接进内容——先一句话说清这份东西解决什么问题。
用分隔符切块，不靠标题层级 每个议题前是一条 ----->o----- 分隔线。纯文本邮件没有 markdown 标题，这是原生的分节手段：让读者能快速跳到关心的那段。长纪要尤其需要——不切块的话，收件人只能从头读到尾。
每条都按「标签 → 谁 → 做了什么 → 结论」 PCI v9 Status: Bjorn Helgaas finished reviewing v8, and David Matlack posted v9 addressing all feedback. All major design questions raised on v8 have been resolved. 冒号前是状态标签（扫读定位），中间点名到人加动词，最后一句给结论。三段式，一眼看完。
归属必须钉死：谁说、谁负责 全文用 David Matlack clarified that / Samiullah Khawaja noted that 这类句式。动词本身就携带信息——clarified（澄清）比 said 有分量，noted（指出）暗示这是个待处理的信息点。多人讨论的纪要最忌「据说」「有人提到」——出现这种措辞，读者就不知道该找谁。
下一步必须带人和时间 Pasha will wait a few days for Bjorn's final review tags before applying v9 to liveupdate/next, aiming to land the series within the next 1-2 weeks (ideally next week prior to 7.3-rc6) for Linux 7.4. 主语是人（Pasha will），不是被动的 will be done；时间给了三层——等多久（a few days）、目标窗口（next 1-2 weeks）、硬约束（prior to 7.3-rc6）、最终目标（Linux 7.4）。没有人和时间的「下一步」，等于没有下一步。
✍️ 仿写模板
/ column★ 可套用的纪要骨架
开头 Here are the notes from our <会议名> call held on <日期>. These notes are intended to bring those who could not attend up to speed and to keep the momentum going between meetings.
每条议题 <议题名> — <状态标签>: <谁> <做了什么>. <结论一句话>.
每条待办 <谁> will <做什么> before <节点>, aiming to <目标> within <时间窗> (ideally <硬期限>) for <最终目标>.
仿写示范 Landing: David will rework the CSI-2 RX format table before the next call, aiming to post v4 within two weeks (ideally before the rc6 cutoff) for the 7.4 merge window.
✨ 辅助彩蛋：标题解析
/ column★ [Hypervisor Live Update] Notes from September 21, 2026
两套前缀，两种性质 内核邮件标题里有两套前缀约定：
[PATCH v9 00/13] 这种方括号加 PATCH 是待合入的补丁系列；[Hypervisor Live Update] 这种方括号加工作组名，是非补丁邮件——会议纪要、状态更新、RFC 召集。 为什么有用 维护者扫一眼标题就知道该不该点开：方括号里是工作组名而不是 PATCH，说明这不是需要评审的代码，而是组织性信息。写这类邮件时沿用同一个方括号标签，还能让同一条线的历史邮件聚在一起，方便按标题检索。
✍️ 今日练习
/ column✍️ 假设你刚开完一次相机链路的上游对齐会，产出了三件事：① 格式命名方案已收敛；② 有人指出 SerDes 侧的对齐校验还没覆盖；③ 下一位负责人要改完再发下一版。请按上面的骨架，用英文写三条纪要。
💡 显示答案
参考作答（仿写示范，非原文）：① Format Naming: The group agreed on a single naming scheme for the eight RGBIr formats; no further design questions remain. ② SerDes Coverage: Laurent noted that the alignment check on the deserializer side is not covered yet, and asked for it to be added before the next revision. ③ Next Revision: Rishikesh will rework the format table and the SerDes check before the next call, aiming to post v2 within two weeks (ideally before the rc6 cutoff) for the 7.4 merge window.
📖 原文：These notes are intended to bring those who could not attend up to speed and to keep the momentum going between meetings. ... * Landing Timeline: Pasha will wait a few days for Bjorn's final review tags before applying v9 to liveupdate/next, aiming to land the series within the next 1-2 weeks (ideally next week prior to 7.3-rc6) for Linux 7.4.
📎 原文引用 每日一句：Notes nobody can act on are just a transcript. Name the person, name the date.
仿写示范