From: Daniel Berlin <dberlin@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
cgf@redhat.com, gdb@sources.redhat.com
Subject: Re: bugzilla (was Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3)
Date: Mon, 22 Sep 2003 22:54:00 -0000 [thread overview]
Message-ID: <B5FCEF28-ED4F-11D7-8DA5-000A95AF1FAE@dberlin.org> (raw)
In-Reply-To: <vt2he34ehkw.fsf@zenia.home>
On Sep 22, 2003, at 3:41 PM, Jim Blandy wrote:
> Daniel Berlin <dberlin@dberlin.org> writes:
>
>> On Fri, 19 Sep 2003, Michael Elizabeth Chastain wrote:
>>
>>> 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.
>>
>> You can actually even email in attachments, and it'll attach them to
>> the
>> bug.
>
> Cool. I'm sold.
>
I'll try to do a test conversion this weekend and see what happens.
next prev parent reply other threads:[~2003-09-22 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 0:54 Michael Elizabeth Chastain
2003-09-22 3:00 ` Daniel Berlin
2003-09-22 19:45 ` Jim Blandy
2003-09-22 22:54 ` Daniel Berlin [this message]
-- 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=B5FCEF28-ED4F-11D7-8DA5-000A95AF1FAE@dberlin.org \
--to=dberlin@dberlin.org \
--cc=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec@shout.net \
/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