From: Christopher Faylor <cgf@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: bugzilla (was Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3)
Date: Sat, 20 Sep 2003 00:19:00 -0000 [thread overview]
Message-ID: <20030920001921.GA17614@redhat.com> (raw)
In-Reply-To: <vt2brtgfhuf.fsf@zenia.home>
On Fri, Sep 19, 2003 at 07:01:44PM -0500, Jim Blandy wrote:
>Christopher Faylor <cgf@redhat.com> writes:
>
>> On Fri, Sep 19, 2003 at 06:29:09PM -0400, Michael Elizabeth Chastain wrote:
>> >I think it's good to send the patch to gdb-patches as usual,
>> >and then mail to gdb-gnats with a URL that points to the patch.
>> >That means you have to for the patch to show up in the gdb-patches
>> >archive, but that takes just a few seconds.
>>
>> Just as an aside, I'm wondering if it is time to consider switching
>> to bugzilla. I think bugzilla handles this issue a little better.
>
>Does bugzilla allow you to CC the bug on E-mail messages, the way
>GNATS does? I love that, and I haven't seen bugzilla do it.
You mean can you send email to bugzilla and have it file the bug?
I think Daniel Berlin has that set up for gcc, yes.
cgf
next prev parent reply other threads:[~2003-09-20 0:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 22:29 macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3 Michael Elizabeth Chastain
2003-09-19 23:58 ` Christopher Faylor
2003-09-20 0:04 ` Jim Blandy
2003-09-20 0:19 ` Christopher Faylor [this message]
2003-09-22 2:55 ` Daniel Berlin
2003-09-20 4:39 ` Daniel Jacobowitz
2003-09-22 3:05 ` Daniel Berlin
2003-09-22 3:32 ` Daniel Jacobowitz
2003-09-20 0:54 bugzilla (was Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3) Michael Elizabeth Chastain
2003-09-22 3:00 ` Daniel Berlin
2003-09-22 19:45 ` Jim Blandy
2003-09-22 22:54 ` Daniel Berlin
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=20030920001921.GA17614@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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