From: Daniel Berlin <dberlin@dberlin.org>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Web part of bugzilla is ready (fwd)
Date: Sat, 08 Feb 2003 17:06:00 -0000 [thread overview]
Message-ID: <9069BFCE-3B87-11D7-B618-000393575BCC@dberlin.org> (raw)
In-Reply-To: <20030208163718.GA8950@redhat.com>
On Saturday, February 8, 2003, at 11:37 AM, Christopher Faylor wrote:
> On Sat, Feb 08, 2003 at 11:25:40AM -0500, Christopher Faylor wrote:
>> Ok. I just didn't want to leave the impression that it was stalled on
>> the sysadmin side of things.
>
> Actually, on reading this, it sounds like I was saying things were
> stalled
> on Daniel's end, which wasn't my intent either. It sounds like we're
> close
> to getting bugzilla operational, in fact.
Yup.
I just like to make sure it works perfectly on my system before moving
it to sources.
I hadn't touched that gnats *email* parsing script in a while, and I
had to merge it with the latest version of the gnats db conversion
script (The email parsing script is a bastardized version of the gnats
db->bugzilla db converter script i wrote).
Thus, i'm running it through random emails selected from the gcc-gnats
list by hand to make sure it works.
>
> cgf
next prev parent reply other threads:[~2003-02-08 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 4:17 Daniel Berlin
2003-02-04 4:36 ` Christopher Faylor
2003-02-05 8:04 ` Jason Molenda
2003-02-06 0:31 ` Daniel Berlin
2003-02-08 2:45 ` Christopher Faylor
2003-02-08 4:53 ` Daniel Berlin
2003-02-08 16:25 ` Christopher Faylor
2003-02-08 16:36 ` Christopher Faylor
2003-02-08 17:06 ` Daniel Berlin [this message]
2003-02-10 1:23 ` Daniel Berlin
2003-02-21 1:13 ` Christopher Faylor
2003-02-08 12:39 ` Joseph S. Myers
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=9069BFCE-3B87-11D7-B618-000393575BCC@dberlin.org \
--to=dberlin@dberlin.org \
--cc=cgf@redhat.com \
--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).