From: Michael Elizabeth Chastain <mec@shout.net>
To: jimb@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3
Date: Fri, 19 Sep 2003 22:29:00 -0000 [thread overview]
Message-ID: <200309192229.h8JMT9q0021832@duracef.shout.net> (raw)
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.
Michael C
next reply other threads:[~2003-09-19 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 22:29 Michael Elizabeth Chastain [this message]
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
2003-09-22 2:55 ` macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3 Daniel Berlin
2003-09-20 4:39 ` Daniel Jacobowitz
2003-09-22 3:05 ` Daniel Berlin
2003-09-22 3:32 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-09-22 3:39 Michael Elizabeth Chastain
[not found] <200309192212.h8JMCdfS021605@duracef.shout.net>
2003-09-19 22:16 ` Jim Blandy
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=200309192229.h8JMT9q0021832@duracef.shout.net \
--to=mec@shout.net \
--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