From: Steven Grimm <koreth@midwinter.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Integrating the kernel tree and lkml
Date: Mon, 13 Aug 2007 10:08:24 +0800 [thread overview]
Message-ID: <46BFBD18.50007@midwinter.com> (raw)
In-Reply-To: <9e4733910708121731h1245eab3h9e331de8285daf8a@mail.gmail.com>
Jon Smirl wrote:
> 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.
>
That sounds a lot like the "notes" proposal that was discussed on this
list a couple months back. It included a notion of "soft references"
which were used to tie commits to the note objects; that would
presumably apply to the mailing list messages as well. IIRC the
implementation that was proposed had some issues. Not sure what happened
to it in the end.
Such a capability would also be a good integration point for bug
tracking systems.
-Steve
next prev parent reply other threads:[~2007-08-13 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 0:31 Integrating the kernel tree and lkml Jon Smirl
2007-08-13 2:08 ` Steven Grimm [this message]
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=46BFBD18.50007@midwinter.com \
--to=koreth@midwinter.com \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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).