git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Integrating the kernel tree and lkml

From
Jon Smirl <jonsmirl@gmail.com>
Date
Aug 13, 2007, 00:31 UTC
Message-ID
<9e4733910708121731h1245eab3h9e331de8285daf8a@mail.gmail.com>

The thread about using a news reader to read the git history caused me wonder if are other synergies between git and the mail/news world.

You could load the lkml history into the git db along with the kernel tree. Then process the mailing list history to tie discussion threads to commits. As you look at commits with gitk you could also see the relevant messages on lkml.

Of course post processing lkml may not tie the threads to the commits very well. But if we built something like this we could start putting the right clues into the threads to make sure they get linked to the commits properly in the future. For example you could link an existing thread by including the sha1 of the commit in a reply.

The git kernel history is about three years old. How big is three years of lkml put into git and packed? A db like this may not be for everyone but it could always live on a server with web access.

-- 
Jon Smirl
jonsmirl@gmail.com
Next: Steven Grimm
Message 1 of 3 in “Integrating the kernel tree and lkml”
  1. Jon SmirlAug 13, 2007
  2. Steven GrimmAug 13, 2007
  3. Johannes SchindelinAug 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.