All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy D. Witham" <wookie@osdl.org>
To: Larry McVoy <lm@bitmover.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	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: 02 Jan 2003 08:15:36 -0800	[thread overview]
Message-ID: <1041524136.1491.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20030102025605.GE23419@work.bitmover.com>

  Sorry for the slow response I'm on vacation and sharing
the computer with 4 teenagers who are all addicted
to IRC.  But I think that Martin can get this done.

  Martin if you need help from my folks please contact
them and get this done.

Tim

On Wed, 2003-01-01 at 18:56, Larry McVoy wrote:
> > 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?
-- 
Timothy D. Witham - Lab Director - wookie@osdlab.org
Open Source Development Lab Inc - A non-profit corporation
15275 SW Koll Parkway - Suite H - Beaverton OR, 97006
(503)-626-2455 x11 (office)    (503)-702-2871     (cell)
(503)-626-2436     (fax)


      parent reply	other threads:[~2003-01-02 17:10 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
2003-01-02 16:15           ` Timothy D. Witham [this message]

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=1041524136.1491.2.camel@localhost.localdomain \
    --to=wookie@osdl.org \
    --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=mbligh@aracnet.com \
    --cc=rddunlap@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.