Lines Matching refs:org
41 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
94 ``quilt`` <https://savannah.nongnu.org/projects/quilt> 另外一个流行的选择。
136 https://lkml.kernel.org/ 重定向，以确保链接不会过时。
220 的维护人员，那么Andrew Morton（akpm@linux-foundation.org）将充当最后的维护
223 您通常还应该选择至少一个邮件列表来接收补丁集的。linux-kernel@vger.kernel.org
228 许多与内核相关的列表托管在vger.kernel.org上；您可以在
229 http://vger.kernel.org/vger-lists.html 上找到它们的列表。不过，也有与内核相关
235 地址是 <torvalds@linux-foundation.org> 。他收到的 e-mail 很多，所以一般
238 如果您有修复可利用安全漏洞的补丁，请将该补丁发送到 security@kernel.org。对于
244 Cc: stable@vger.kernel.org
255 更改复制到 linux-api@vger.kernel.org。
258 trivial@kernel.org，那里专门收集琐碎的补丁。下面这样的补丁会被看作“琐碎的”
278 trivial@kernel.org邮件列表的目的是针对这样的补丁，为提交者提供一个中心，来
367 Signed-off-by: Random J Developer <random@developer.example.org>
382 Signed-off-by: Random J Developer <random@developer.example.org>
383 [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h]
384 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
443 Co-developed-by: First Co-Author <first@coauthor.example.org>
444 Signed-off-by: First Co-Author <first@coauthor.example.org>
445 Co-developed-by: Second Co-Author <second@coauthor.example.org>
446 Signed-off-by: Second Co-Author <second@coauthor.example.org>
447 Signed-off-by: From Author <from@author.example.org>
451 From: From Author <from@author.example.org>
455 Co-developed-by: Random Co-Author <random@coauthor.example.org>
456 Signed-off-by: Random Co-Author <random@coauthor.example.org>
457 Signed-off-by: From Author <from@author.example.org>
458 Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
459 Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
602 可以使用 https://lkml.kernel.org/ 重定向器（例如，在封面电子邮件文本中）
652 <https://www.ozlabs.org/~akpm/stuff/tpp.txt>
655 <https://web.archive.org/web/20180829112450/http://linux.yyz.us/patch-format.html>
670 NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
671 <https://lkml.org/lkml/2005/7/11/336>
677 <http://lkml.org/lkml/2005/4/7/183>