From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Integrating the kernel tree and lkml
Date: Sun, 12 Aug 2007 20:31:22 -0400 [thread overview]
Message-ID: <9e4733910708121731h1245eab3h9e331de8285daf8a@mail.gmail.com> (raw)
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 reply other threads:[~2007-08-13 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 0:31 Jon Smirl [this message]
2007-08-13 2:08 ` Integrating the kernel tree and lkml Steven Grimm
2007-08-13 11:04 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4733910708121731h1245eab3h9e331de8285daf8a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).