From: Alex Schuilenburg <alexs@ecoscentric.com>
To: dkl@redhat.com
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: eCos Bugzilla bugs on http://bugzilla.redhat.com/
Date: Sun, 11 May 2003 10:32:00 -0000 [thread overview]
Message-ID: <3EBE26B4.2020902@ecoscentric.com> (raw)
Hi Dave
Hope you are well and thing at Red Hat are good.
We have a favour to ask. We (the ecos maintainers and eCosCentric) have
set up our own bugzilla system http://bugs.ecos.sourceware.org/ to start
tracking eCos bugs since there are a number of issues, such as site
customizations ,we need resolved that we obviouly realise will not be
possible in Red Hat's commercial system.
Hence we would like to move over the outstanding (non-closed) bugs from
bugzilla.redhat.com into bugs.ecos.sourceware.org. I would like to do
this the easy way, as we previously discussed (when I worked at RH), by
having you export the data as a series of SQL INSERT statements which we
can use to import directly into our mysql database. I won't go into the
hard way, although you can probably guess.
I realize you will have some site customizations so am quite prepared to
do a fair bit of work to massage the exported data into a state that we
can import it. For example:
* userids will not match
* priority and severity will not match
* platforms and host os will not match
etc
My solution, since this is a once off deal, is simply to import the bugs
into a temporary database, to massage the data and tables to match the
setup on bugs.ecos.sourceware.org and then export from the temp to the
actual database. As part of the transfer we would also like to add
notes to the bugzilla.redhat.com bugs, providing the new URL where the
bug has been moved to and setting the state/resolution to CLOSED+MOVED.
Are you able to provide us with a dump of the eCos bugs?
Thanks
-- Alex
next reply other threads:[~2003-05-11 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 10:32 Alex Schuilenburg [this message]
2003-05-19 21:51 ` Alex Schuilenburg
2003-05-19 23:14 ` Alex Schuilenburg
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=3EBE26B4.2020902@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=dkl@redhat.com \
--cc=ecos-maintainers@sources.redhat.com \
/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).