About The Git List
The Git List is a reading room for the Git project's mailing list, git@vger.kernel.org, where Git itself is developed: patches are posted, reviewed and argued over there before they land. Every message since April 2005 is here, threaded and searchable, and new mail arrives from the public archive at lore.kernel.org every hour.
Each morning an AI editor reads the previous day's activity and writes the front page. Stories stay up for a week. Summaries can be wrong or miss nuance, so each one links to the thread it describes.
For agents and tools
Everything on the site is available as JSON, Markdown and an MCP server. The same text is served at /llms.txt.
# The Git List (gitlist.dev)
> Every message on the Git project's development mailing list, git@vger.kernel.org,
> from April 2005 to now, threaded, searchable and updated hourly from lore.kernel.org.
> An AI editor writes a daily front page. People are merged across their addresses
> with git.git's .mailmap.
There are three ways in. Use whichever your tools support; they return the same data.
## 1. MCP server (best if you can connect to one)
Endpoint (Streamable HTTP, no auth): https://gitlist.dev/mcp
{ "mcpServers": { "gitlist": { "url": "https://gitlist.dev/mcp" } } }
Tools:
- search_messages(query, author?, since?, until?, patchesOnly?, sort?, limit?, offset?)
full-text search; query supports "quoted phrases", OR and -exclusions
- get_thread(threadId) a whole thread as Markdown, bodies and patches included
- get_message(messageId) one email
- recent_threads(limit?, before?) threads by latest activity
- find_people(query?, lastYearOnly?, limit?)
- get_person(key) a person's addresses, counts, yearly activity, patch series
(merged or not, acceptance rate), recent emails
- front_page() this week's curated stories
- get_story(storyId) one story in full
A typical session: search_messages -> get_thread on the best hits -> get_person
for the people involved.
## 2. Plain URLs, as Markdown or text (best for fetch-only agents)
Every page has a text version. Add ".md" to the URL, or request it with
"Accept: text/markdown":
- https://gitlist.dev/index.md the front page
- https://gitlist.dev/t/<id>.md a thread
- https://gitlist.dev/s/<id>.md a front-page story
- https://gitlist.dev/u/<key>.md a person (key is their main address, with "@" written "_at_")
- https://gitlist.dev/e/<Message-ID>/txt one email as plain text
Emails use the same URL encoding as lore.kernel.org, so
https://lore.kernel.org/git/<id>/ -> https://gitlist.dev/e/<id>
## 3. JSON API (no key needed)
- GET /api/search?q=...&author=...&since=YYYY-MM-DD&until=YYYY-MM-DD&patches=1&sort=newest&limit=25&offset=0
each result has the thread id and a snippet with matches marked «like this»
- GET /api/threads?limit=50&before=<ISO time> recently active threads
- GET /api/threads/<id> a thread and all its messages
- GET /api/messages?id=<Message-ID> one message
- GET /api/front this week's stories (headline, dek, overview, full summary)
## Web pages
- / front page /threads recent threads
- /t/<id> a thread /search?q= search
- /e/<Message-ID> one email /people the most active people
- /s/<id> a story /u/<key> a person
- /m?id=<Message-ID> redirects to /e/<Message-ID>
Please be gentle: cache what you can. The original archive is https://lore.kernel.org/git/.