From: Larry McVoy <lm@bitmover.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Larry McVoy <lm@bitmover.com>, Andrew Morton <akpm@zip.com.au>,
Dave Jones <davej@codemonkey.org.uk>,
"Timothy D. Witham" <wookie@osdl.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Raw data from dedicated kernel bug database
Date: Wed, 1 Jan 2003 18:56:05 -0800 [thread overview]
Message-ID: <20030102025605.GE23419@work.bitmover.com> (raw)
In-Reply-To: <45160000.1041475166@titus>
> Larry, can I presume that you'll reciprocate, and export whatever you
> do to the data in BK in some argument-free format (probably the same
> one we export to you)?
Yup. A BK database is actually a BK repostory with an SQL layer on
top of it. So all of the stuff you can do with BK you can do with
BK/Database. We can export changes as patches, as flat files, as
associative arrays in perl, take your pick.
> I think the concerns I had about tools going wild are actually fairly
> easy to resolve by making it a pull-pull interchange ... don't know
> why I was thinking of push models.
Cool. I've already tracked down an SQL hacker who is willing to contract
with us to write the scripts to get the data out of your Bugzilla database.
He said that I need to ask you to do this:
shut down the mysql database
grab all the MySQL files and stuff them in a tarball
turn on the mysql database again
Then he can set up a mysql instance here and start hacking on the scripts.
How's that sound?
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-01-02 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 19:40 Raw data from dedicated kernel bug database Larry McVoy
2003-01-01 20:06 ` John Bradford
2003-01-01 21:30 ` Martin J. Bligh
2003-01-01 22:15 ` Larry McVoy
2003-01-02 0:32 ` Martin J. Bligh
2003-01-02 2:03 ` Alan Cox
2003-01-02 0:38 ` Timothy D. Witham
2003-01-02 2:16 ` Larry McVoy
2003-01-02 2:39 ` Martin J. Bligh
2003-01-02 2:56 ` Larry McVoy [this message]
2003-01-02 5:12 ` Martin J. Bligh
2003-01-02 16:15 ` Timothy D. Witham
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=20030102025605.GE23419@work.bitmover.com \
--to=lm@bitmover.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=rddunlap@osdl.org \
--cc=wookie@osdl.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