From: Christopher Faylor <cgf@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: overseers@gcc.gnu.org
Subject: Re: Web part of bugzilla is ready (fwd)
Date: Sat, 08 Feb 2003 16:25:00 -0000 [thread overview]
Message-ID: <20030208162540.GA8744@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0302072346380.5417-100000@dberlin.org>
On Fri, Feb 07, 2003 at 11:53:41PM -0500, Daniel Berlin wrote:
>The second is a more general interface, that can do more (IE do bug
>searches, etc, by email). It just needs a new email address.
>This script is done and ready to go, but secondary, so if you are busy at
>the moment, don't worry about it.
This is easy to set up. I just have to create a gcc-bugzilla alias that
runs this program, similar to the gcc-gnats alias. I'll set up the
alias if you provide the path to the program.
>> 2) Something to generate email when a bug is entered in bugzilla.
>>
>This is already done by bugzilla on its own.
Cool.
>> Neither is hard to do. I can set up 1 immediately, if you want. We can
>> set up a gcc-bugzilla mailing list and have it go directly into your
>> database. Just tell me what program needs to be run.
>
>I shall, the second i have it done.
Ok. I just didn't want to leave the impression that it was stalled on
the sysadmin side of things.
cgf
next prev parent reply other threads:[~2003-02-08 16:25 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 [this message]
2003-02-08 16:36 ` Christopher Faylor
2003-02-08 17:06 ` Daniel Berlin
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=20030208162540.GA8744@redhat.com \
--to=cgf@redhat.com \
--cc=dberlin@dberlin.org \
--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).