05 — Mailing Lists and IRC

This is where the actual engineers writing the compilers and the kernel talk. You will not post here for the first six months. You will lurk. Reading a week of LKML or gcc-devel is the equivalent of shadowing a senior engineer for a month — you see the reasoning, the pushback, the code review culture.

Mailing lists worth lurking

List

What it is

How to read (archive)

Cadence

Linux Kernel Mailing List (LKML)

The main list for kernel development

https://lore.kernel.org/lkml/ · human-readable UI: https://lkml.org/

Firehose. Filter by subsystem.

WG14 (ISO C committee) documents

Standards papers proposing changes to C

https://www.open-std.org/jtc1/sc22/wg14/www/documents

Papers land weekly; the interesting ones show up on HN

gcc-devel

GCC development

https://gcc.gnu.org/lists.html — archives at https://gcc.gnu.org/pipermail/gcc/

Daily

gcc-help

User-facing GCC questions

same list index

Weekly

libc-alpha (glibc)

glibc development

https://sourceware.org/mailman/listinfo/libc-alpha

Daily

musl

musl libc

https://www.openwall.com/lists/musl/

Weekly, high-signal

oss-security

Security advisories from open-source projects

https://oss-security.openwall.org/wiki/mailing-lists/oss-security

Daily

How to read LKML without drowning

  1. Use lore.kernel.org — it groups threads by subject and gives permalinks.

  2. Subscribe to a subsystem, not the whole list. Interesting starters: linux-mm (memory management), io-uring, linux-net, linux-fsdevel.

  3. Read Greg K-H’s weekly summaries via LWN.net (paid but worth it; free after a week).

  4. Do not email until you have read for at least six months. See https://www.kernel.org/doc/html/latest/process/ for the etiquette.

How to read WG14 papers

Papers are named Nxxxx.pdf (e.g., N3096 is the C23 draft). Interesting ones:

  • N3220 — C23 rationale summary

  • N2596 — attributes syntax proposal

  • Any paper by Jens Gustedt (defer semantics, generic selection extensions)

  • Any paper by JeanHeyd Meneide

Index of papers: https://www.open-std.org/jtc1/sc22/wg14/www/docs/

IRC — still alive on Libera.Chat

IRC didn’t die; it moved. Freenode collapsed in 2021; the community migrated to Libera.Chat (https://libera.chat/). Register a nick, use a proper client (weechat or irssi), and consider a persistent bouncer (znc) or Libera’s built-in soju service.

Channel

Server

Focus

##c

Libera.Chat

The main C channel (yes, two # — a “public” channel)

#gcc

Libera.Chat

GCC users and devs

#llvm

Libera.Chat

LLVM/Clang

##linux

Libera.Chat

Kernel-adjacent chat

#musl

Libera.Chat

musl libc

#gdb

Libera.Chat

GDB users and devs

(Invites current; verify via https://libera.chat/guides/ before joining.)

What most people get wrong about lists and IRC

They post before they lurk. The failure mode: a beginner asks something on LKML that the docs answer in the first paragraph, gets [PATCH REJECTED]-style responses, and quits. Read for months. Understand the culture. When you finally have something to contribute (a real bug report, a doc fix, a well-formed patch), you will get in through the front door because you know the rules.

Return to README.md · Next: 06_youtube_communities.md