From: Michael Elizabeth Chastain <mec@shout.net>
To: cgf@redhat.com, jimb@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: bugzilla (was Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3)
Date: Sat, 20 Sep 2003 00:54:00 -0000 [thread overview]
Message-ID: <200309200054.h8K0svr2023791@duracef.shout.net> (raw)
jimb> Does bugzilla allow you to CC the bug on E-mail messages, the way
jimb> GNATS does? I love that, and I haven't seen bugzilla do it.
Yes, for example:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
For a gcc bug where Chris and I e-mailed in some comments.
Michael C
next reply other threads:[~2003-09-20 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 0:54 Michael Elizabeth Chastain [this message]
2003-09-22 3:00 ` Daniel Berlin
2003-09-22 19:45 ` Jim Blandy
2003-09-22 22:54 ` Daniel Berlin
-- strict thread matches above, loose matches on Subject: below --
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 ` bugzilla (was Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3) Christopher Faylor
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=200309200054.h8K0svr2023791@duracef.shout.net \
--to=mec@shout.net \
--cc=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