今日重点：💬 地道表达——上一篇地道表达学的是硬件语境里的惯用语。 今天学人际语境：有人给 buddy 分配器提了一个大胆的 RFC， 两位维护者把它温和劝退，三封邮件里一个 no 都没出现。 六句话，逐字取自原文——这是内核邮件列表最实用的一课：怎么否定一个想法，而不否定提出它的人。
📖 原文（真实邮件，逐字引用）
/ sectionThank you for posting the idea. Like Rik suggested, it is better to focus on one thing at a time. I think improving anti-fragmentation at pageblock level is high priority at the moment. ... I am not sure how your bucket idea is better than the existing pageblock design, because the biggest issue in anti-fragmentation is unmovable pages spreading across the entire physical memory space to prevent high order page allocation ... Maybe you can compare your idea with Rik's series and tell us the pros and cons of both. :)
出处：三封邮件，同一线程 [RFC NO CODE] [DISCUSSION] Anti-fragmenting ordered buddy allocator。 原帖 Dev Jain（ARM），10-12 05:54 北京；Rik van Riel 回复，06:00 北京；Zi Yan（NVIDIA）回复，07:05 北京。 上面引的是 Zi Yan 那一封——练习题的 source 链接直接指向它，点开就能看到这些原句。
💬 表达一：先认劳动，再谈想法
/ column★ Thank you for posting the idea.
原句 Thank you for posting the idea.
中文与语境 提出一个 RFC 意味着写了文档、跑了数据、把问题想清楚了。这句话承认的是这部分的劳动。它把「人」和「想法」先分开——想法等下要否掉，但劳动先记下。内核列表里几乎所有的「软性驳回」都从这一句开始。
怎么用 要否掉别人的方案时，第一句先认劳动，可用变体：Thank you for posting the idea / for the detailed writeup / for taking the time to run these numbers.
💬 表达二：把「你的先放放」说成常识
/ column★ it is better to focus on one thing at a time
原句 Like Rik suggested, it is better to focus on one thing at a time. I think improving anti-fragmentation at pageblock level is high priority at the moment.
中文与语境 妙在两处。一是 it is better to… 这个无人称句式：它陈述「更好的做法长这样」，而不说「你不该这么做」——主语一没，指责感就没了。二是 high priority at the moment：把优先级说成「当下」的客观状态，而不是对该方案价值的判决。附带一提，Like Rik suggested 先把自己藏到别人身后，进一步降低对抗感。
怎么用 不要说 you should stop；说 it is better to … at the moment。句式的软，和判断的硬，是两件事。
💬 表达三：反对的黄金公式
/ column★ I am not sure how X is better than Y, because …
原句 I am not sure how your bucket idea is better than the existing pageblock design, because the biggest issue in anti-fragmentation is unmovable pages spreading across the entire physical memory space to prevent high order page allocation and I do not see how your idea could contaminate unmovable pages.
中文与语境 注意它没说 your idea is wrong。I am not sure how… 把不确定留在自己身上，但 because 后面立刻给出实打实的技术理由——不可移动页会散布到整个物理内存空间、挡住高阶分配。这就是内核 review 的标准做法：礼貌交给句式，说服力交给论据，两件事分开做。
怎么用 I am not sure how X is better than Y, because … 直接可套。后半句必须是技术事实，不能也是情绪。
💬 表达四：请人先看自己的东西
/ column★ Could I convince you to take a look at these patches?
原句 Could I convince you to take a look at these patches?
中文与语境 这是 Rik 回复里的第一句。他没有说 please review my patches，而是用 Could I convince you to…——把自己放在「需要说服对方」的位置上，给对方留足说 no 的余地。紧接着另起一行把链接贴出来，不让人去找。
怎么用 想让人先看你的东西：Could I convince you to take a look at …? 它同时完成了「请求」和「不施压」两件事。
💬 表达五：用 we 谈优先级
/ column★ That is probably what we want to get in first.
原句 At the moment, anti-fragmentation is only preventing mixing movable and unmovable pages in a pageblock. Rik's series[3] is doing additional work to keep unmovable page allocation within a unmovable pageblock, further reducing fragmentation. That is probably what we want to get in first.
中文与语境 前一句先用事实铺路（Rik 的系列已经在做这件事），后一句才给结论。结论里塞了三个软化词：we（不是 you）、probably（不是 certainly）、first（不是 instead）。于是「你的先等等」听起来是团队共识，而不是个人裁决。
怎么用 要压别人的优先级时，先说清「已经有人在做什么」，再用 we / probably / first 收口。
💬 表达六：把驳回变成一份作业
/ column★ Maybe you can compare … and tell us the pros and cons of both. :)
原句 Maybe you can compare your idea with Rik's series and tell us the pros and cons of both. :)
中文与语境 结尾这一句最值得学。它把「驳回」变成了一份交给对方的作业：你去把两者对比一下，然后回来告诉我们优劣。于是讨论没有被关死，提出者拿到了下一步动作，而不是被晾在原地。分号笑脸在内核列表里很常见，专门用来软化语气。
怎么用 拒绝的收尾永远要给一个可执行的动作，不要只说 not now。Maybe you can … and tell us … 是好用的模板。
✨ 辅助彩蛋：提大改动时，怎么露出人味
/ section★ because I like to torture myself / kept digging the rabbit hole
原句 I just took up the challenge of anti-fragmentation (because I like to torture myself) and kept digging the rabbit hole.
中文与语境 提一个「要动分配器核心算法」的大改动，最怕显得「我要来改造你们的东西」。Dev Jain 用自嘲把姿态放低：I like to torture myself（我这是自找苦吃）、kept digging the rabbit hole（越挖越深停不下来）。自嘲式开场是 RFC 里降低对抗感的常用手法——先承认这事麻烦、自己也知道难，比一上来讲道理更容易被听进去。
顺带一个文化彩蛋 Rik van Riel 的邮件签名是 All Rights Reversed.——把 Reserved 反着写。内核邮件列表上这类玩笑签名很常见，看到不必困惑，它就是一个签名。
✍️ 今日练习
/ column✍️ 你是子系统维护者，有人提了一个方向不同的大改动（RFC）。用今天学的句式写四句英文：① 先认下对方的工作；② 说明「一次专注一件事」更好，并点出当前的高优先级；③ 礼貌指出你没看出它比现有设计好在哪，并给出技术理由；④ 给对方一个可执行的下一步。
💡 显示答案
参考作答（仿写示范，非原文）：① Thank you for posting the idea. ② Like others have suggested, it is better to focus on one thing at a time -- improving X at the Y level is high priority at the moment. ③ I am not sure how your approach is better than the existing Z design, because <technical reason: e.g. it does not prevent unmovable pages from spreading across the physical memory space>. ④ Maybe you can compare the two approaches and tell us the pros and cons of both. :)
📖 原文：Thank you for posting the idea. / Like Rik suggested, it is better to focus on one thing at a time. I think improving anti-fragmentation at pageblock level is high priority at the moment. / I am not sure how your bucket idea is better than the existing pageblock design, because the biggest issue in anti-fragmentation is unmovable pages spreading across the entire physical memory space to prevent high order page allocation and I do not see how your idea could contaminate unmovable pages. / Maybe you can compare your idea with Rik's series and tell us the pros and cons of both. :)
📎 原文引用 每日一句：Saying no is easy. Saying it so the other person comes back with a better patch is the skill.
仿写示范