{"thread":{"id":"9509","subject":"Integrating the kernel tree and lkml","startedAt":"2007-08-13T00:31:22Z","lastAt":"2007-08-13T11:04:54Z","messageCount":3,"participants":["Jon Smirl","Steven Grimm","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"50608","messageId":"9e4733910708121731h1245eab3h9e331de8285daf8a@mail.gmail.com","threadId":"9509","inReplyTo":null,"subject":"Integrating the kernel tree and lkml","fromName":"Jon Smirl","fromEmail":"jonsmirl@gmail.com","sentAt":"2007-08-13T00:31:22Z","receivedAt":"2007-08-13T00:31:22Z","isPatch":false,"sender":{"key":"jonsmirl@gmail.com","avatar":"https://gravatar.com/avatar/cff3bf5bfdfa6708b905712ff91f0f9b8aaca161659f38c02b787920d5d28b7e?d=mp&s=160"},"body":"The thread about using a news reader to read the git history caused me\nwonder if are other synergies between git and the mail/news world.\n\nYou could load the lkml history into the git db along with the kernel\ntree. Then process the mailing list history to tie discussion threads\nto commits. As you look at commits with gitk you could also see the\nrelevant messages on lkml.\n\nOf course post processing lkml may not tie the threads to the commits\nvery well. But if we built something like this we could start putting\nthe right clues into the threads to make sure they get linked to the\ncommits properly in the future. For example you could link an existing\nthread by including the sha1 of the commit in a reply.\n\nThe git kernel history is about three years old. How big is three\nyears of lkml put into git and packed? A db like this may not be for\neveryone but it could always live on a server with web access.\n\n-- \nJon Smirl\njonsmirl@gmail.com\n"},{"id":"50612","messageId":"46BFBD18.50007@midwinter.com","threadId":"9509","inReplyTo":"9e4733910708121731h1245eab3h9e331de8285daf8a@mail.gmail.com","subject":"Re: Integrating the kernel tree and lkml","fromName":"Steven Grimm","fromEmail":"koreth@midwinter.com","sentAt":"2007-08-13T02:08:24Z","receivedAt":"2007-08-13T02:08:24Z","isPatch":false,"sender":{"key":"koreth@midwinter.com","avatar":"https://gravatar.com/avatar/71b4d2e8b62f168bdc9e9205341159e3567003b4f9e2127c617c5fa0a1f5bad2?d=mp&s=160"},"body":"Jon Smirl wrote:\n> You could load the lkml history into the git db along with the kernel\n> tree. Then process the mailing list history to tie discussion threads\n> to commits. As you look at commits with gitk you could also see the\n> relevant messages on lkml.\n>   \n\nThat sounds a lot like the \"notes\" proposal that was discussed on this \nlist a couple months back. It included a notion of \"soft references\" \nwhich were used to tie commits to the note objects; that would \npresumably apply to the mailing list messages as well. IIRC the \nimplementation that was proposed had some issues. Not sure what happened \nto it in the end.\n\nSuch a capability would also be a good integration point for bug \ntracking systems.\n\n-Steve\n"},{"id":"50632","messageId":"Pine.LNX.4.64.0708131204220.25989@racer.site","threadId":"9509","inReplyTo":"46BFBD18.50007@midwinter.com","subject":"Re: Integrating the kernel tree and lkml","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-08-13T11:04:54Z","receivedAt":"2007-08-13T11:04:54Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 13 Aug 2007, Steven Grimm wrote:\n\n> Jon Smirl wrote:\n> > You could load the lkml history into the git db along with the kernel\n> > tree. Then process the mailing list history to tie discussion threads\n> > to commits. As you look at commits with gitk you could also see the\n> > relevant messages on lkml.\n> \n> That sounds a lot like the \"notes\" proposal that was discussed on this \n> list a couple months back. It included a notion of \"soft references\" \n> which were used to tie commits to the note objects; that would \n> presumably apply to the mailing list messages as well. IIRC the \n> implementation that was proposed had some issues. Not sure what happened \n> to it in the end.\n\nFWIW I planned to continue working on the notes post 1.5.3.\n\nCiao,\nDscho\n"}]}