From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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, 01 Jan 2003 21:12:31 -0800 [thread overview]
Message-ID: <47690000.1041484350@titus> (raw)
In-Reply-To: <20030102025605.GE23419@work.bitmover.com>
> 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.
OK, something like that sounds good to me.
> 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?
I'll leave the details to the database guys at OSDL, but I presume they
do backups in a similar fashion already, so ...
M.
next prev parent reply other threads:[~2003-01-02 5:04 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
2003-01-02 5:12 ` Martin J. Bligh [this message]
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=47690000.1041484350@titus \
--to=mbligh@aracnet.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.