From: Larry McVoy <lm@bitmover.com>
To: "Timothy D. Witham" <wookie@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Larry McVoy <lm@bitmover.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Andrew Morton <akpm@zip.com.au>,
Dave Jones <davej@codemonkey.org.uk>,
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:16:37 -0800 [thread overview]
Message-ID: <20030102021637.GA23419@work.bitmover.com> (raw)
In-Reply-To: <1041467938.1541.2.camel@localhost.localdomain>
Thanks Tim!
On Wed, Jan 01, 2003 at 04:38:58PM -0800, Timothy D. Witham wrote:
> The data is there for everybody. As long as we can automate the
> extraction I don't see any issue with multiple people extracting
> and using with other tools. Data and manure only work if you
> can spread it around.
That is a great quote, mind if I stick on my quotes page?
> My opinion is that the more uses of the data the better. So
> the question is, "What does Larry need to make this happen?".
If your guys are too busy to figure out how to do this, since I'm asking
you to do something for me, how about they give me a snapshot of the
DB's, I'll get one of my guys to tinker with it enough that they can
get the data out, and then we'll provide a script to do this on an
ongoing basis. So you could run
cd /home/bugme
make export
out of cron and it would serve up a tarball that anyone could eat.
Anyone else who is interested in the data can contact me with their
desired export format and I'm merge sort over the requests. If
nobody cares then what I'd create is a directory tree that looked
like:
bugdb/
bugs/
MM-YYYY/
bug1.field1
bug1.field2
...
bug1.fieldN
bug2.field1
bug2.field2
...
bug2.fieldN
...
users/
user1.field1
...
user1.fiendN
user2.field1
...
user2.fiendN
...
In other words, a zillion little files, a cluster of files per bugid,
with each file in the cluster representing a field in the bug. That
way there are no parse/unparse issues (if we used XML then we need to
unXML it to get it into some other DB). Each MM-YYYY directory is
used to store all bugs created in that month (so we don't end up with
one directory with 10 million files in it).
It wastes tons of space because there will be zillions of these files
but it's a tarball and it's only for import/export. And it has to be
the most neutral format.
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:08 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 [this message]
2003-01-02 2:39 ` Martin J. Bligh
2003-01-02 2:56 ` Larry McVoy
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=20030102021637.GA23419@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