$ git log --author="neild" --all --oneline
Every morning, RepoJournal's newsroom reads what shipped across the open-source projects developers depend on — and writes the wire. Your commits kept making the news. This is your clippings file: the stories where your work was the story.
27
stories filed
16
daily wires
$ grep -rn "author: neild" wires/ | sort -r
HTTP/1 body deadlock fix, gopls fillstruct stack overflow, and importer fork removal
- http2: drop benchmarks golang/net
Compiler inlines recover, http.Transport.CancelRequest becomes a no-op
- net/http: make Transport.CancelRequest into a no-op golang/go
- net/http/httputil/reverseproxy: preserve original header on 1xx golang/go
- quic: add Stream.StopSending, and rework stream/application errors golang/net
- _content/doc/security: decisions: add general principles golang/website
- _content/doc/security: document security bug submission retention golang/website
net/http aborts writes on dead connections, breaks solaris fuzz test
unicode/norm composition bugs shake the foundation
Go Deprecates HTTP/2 Transport Direct Use
- http2: deprecate Transport and Server golang/net
GO CLEANUP: SPLITPHASE GONE, RISCV64 FASTER
- data/reports/GO-2026-5026: add additional attribution golang/vulndb
GO'S SYNC.ONCE PANIC TRAP
GO COMPILER REWRITES SPLIT FOR PARALLEL BUILDS
GO STRIPS LEGACY CODE.GOOGLE.COM PATHS, HTTP/2 HOST HEADER FIX LANDS
GO AUTH CREDENTIALS FIXED, JSON V2 DROPS CYCLE GUARANTEE
GO FIXES BREAKING ABI REGRESSION AND LOCKS DOWN REVERSE PROXY COOKIE HANDLING
GO REWORKS HTTP/3 REGISTRATION, KILLS GLOBAL STATE IN MODULE LOADER
COMPILER SHRINKS CODE SIZE WHILE QUIC FIXES BUSY-LOOP HANGS
GO PATCHES HTTP/2 BYPASS IN REVERSEPROXY, COMPILER GAINS FUSION MATH
NET/HTTP STOPS RELYING ON REQUEST BODY IMMUTABILITY
- net/http: don't rely on server request body not changing golang/go
- data/reports: add GO-2026-5970 golang/vulndb
- data/reports: add GO-2026-5942 golang/vulndb
- _content/doc/security: decision: malicious code golang/website
A page like this — but yours, daily.
These clippings exist because your work kept showing up in other projects' wires. RepoJournal can write the whole journal: your commits, PRs and releases, turned into a daily devlog you never have to write.
Free. We read your public contributions only - private repos are never summarised.