From: Jim Blandy <jimb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
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:16:00 -0000 [thread overview]
Message-ID: <vt2pthwfmuf.fsf@zenia.home> (raw)
In-Reply-To: <200309192212.h8JMCdfS021605@duracef.shout.net>
This points out an interesting issue. I can attach a patch to a PR in
two ways, neither of which are really satisfactory:
- I can attach the patch directly to the PR, which causes GNATS to
generate E-mail messages that refer to "attachments" that are not
present in the message.
- Or, if I'm replying to a PRMS message, I can attach the patch to the
message, which results in the patch not appearing as an attachment
to the PR itself.
Hmph. I could always just do both, I suppose.
next parent reply other threads:[~2003-09-19 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200309192212.h8JMCdfS021605@duracef.shout.net>
2003-09-19 22:16 ` Jim Blandy [this message]
2003-09-19 22:29 Michael Elizabeth Chastain
2003-09-19 23:58 ` Christopher Faylor
2003-09-20 0:04 ` Jim Blandy
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-22 3:39 Michael Elizabeth Chastain
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=vt2pthwfmuf.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb@sources.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