惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
Microsoft Azure Blog
Microsoft Azure Blog
G
Google Developers Blog
宝玉的分享
宝玉的分享
V
V2EX
MongoDB | Blog
MongoDB | Blog
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Microsoft Security Blog
Microsoft Security Blog
博客园 - 聂微东
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
IT之家
IT之家
Martin Fowler
Martin Fowler
大猫的无限游戏
大猫的无限游戏
Recent Announcements
Recent Announcements
人人都是产品经理
人人都是产品经理
博客园 - 司徒正美
美团技术团队
F
Fortinet All Blogs
N
Netflix TechBlog - Medium
Hugging Face - Blog
Hugging Face - Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
B
Blog RSS Feed

The Linux Kernel Archives

Active kernel releases The Linux Kernel Organization About Linux Kernel Contacts Frequently asked questions Linux.dev mailing list service Git mirror available in Beijing Code of Conduct List archives on lore.kernel.org Minor changes to kernel tarball releases Best way to do linux clones for your CI Nitrokey digital tokens for kernel developers Linux kernel releases PGP signatures RC tarballs and patches starting with 4.12-rc1 If you got "BAD Signature" this morning Fast new frontends with Packet Shutting down FTP services Gandi.net TLS certificates Cloning Linux from a bundle Introducing Fastly CDN Hurr, Durr Im'a Sheep FTP limited on mirrors.kernel.org Heartbleed statement Happy new year and good-bye bzip2 New frontend and googlesource.com Mirroring kernel.org repositories Fifty shades of Tux XZ by default and JSON /pub tree resync-ing Cleanroom styles
Get notifications for your patches
2018-12-13 · via The Linux Kernel Archives

We are trialing out a new feature that can send you a notification when the patches you send to the LKML are applied to linux-next or to the mainline git trees. If you are interested in trying it out, here are the details:

  • The patches must be sent to the LKML (linux-kernel@vger.kernel.org).
  • One of the cc's must be notify@kernel.org (Bcc will not work).
  • Alternatively, there should be a "X-Patchwork-Bot: notify" email header.
  • The patches must not have been modified by the maintainer(s).
  • All patches in the series must have been applied, not just some of them.

The last two points are important, because if there are changes between the content of the patch as it was first sent to the mailing list, and how it looks like by the time it is applied to linux-next or mainline, the bot will not be able to recognize it as the same patch. Similarly, for series of multiple patches, the bot must be able to successfully match all patches in the series in order for the notification to go out.

If you are using git-format-patch, it is best to add the special header instead of using the Cc notification address, so as to avoid any unnecessary email traffic:

--add-header="X-Patchwork-Bot: notify"

You should receive one notification email per each patch series, so if you send a series of 20 patches, you will get a single email in the form of a reply to the cover letter, or to the first patch in the series. The notification will be sent directly to you, ignoring any other addresses in the Cc field.

The bot uses our LKML patchwork instance to perform matching and tracking, and the source code for the bot is also available if you would like to suggest improvements.