From: Ian Lance Taylor <ian@airs.com>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: overseers@gcc.gnu.org
Subject: Re: Raw DB access possible ?
Date: Thu, 06 Jun 2013 17:05:00 -0000 [thread overview]
Message-ID: <m34ndbw4on.fsf@pepe.airs.com> (raw)
In-Reply-To: <20130606062420.GA26561@opentech.at> (Nicholas Mc Guire's message of "Thu, 6 Jun 2013 08:24:21 +0200")
Nicholas Mc Guire <der.herr@hofr.at> writes:
> We are looking at using bug tracking data for bug prediction as well as
> estimation of residual bug probability for gcc qualification. While the
> current bug-tracking database interface is quite powerful nottably with
> the advanced search it is not suitable for some of the correlation queries
> we would like to do. Is there any chance of getting a copy of the current
> raw database or some read-only raw access to the bug-tracking database ?
No, sorry. The database includes user passwords and we don't have an
easy way to separate them out.
Ian
prev parent reply other threads:[~2013-06-06 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 6:24 Nicholas Mc Guire
2013-06-06 17:05 ` Ian Lance Taylor [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=m34ndbw4on.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=der.herr@hofr.at \
--cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).