From: David Carlton <carlton@math.stanford.edu>
To: gdb <gdb@sources.redhat.com>
Subject: external bugs
Date: Fri, 14 Mar 2003 17:40:00 -0000 [thread overview]
Message-ID: <ro1wuj1j18t.fsf@jackfruit.Stanford.EDU> (raw)
What was the consensus as to how we should mark external PR's, for use
with XFAILed tests? The reason why I ask is that I wanted to file a
PR about 'break Class.method' failing in Java: this bug (which is
different from the 'break Class.method(args)' bug in PR 1039 that I've
just submitted a patch for) is due to a bug in GCJ, that I've just
filed a PR for.
But when I went to create a GDB bug, I noticed that 'external' was a
category. That might make sense, but I'd really prefer for this bug
to be in the 'java' category. Would adding an 'external' class make
sense? Looking at the other classes (doc-bug, sw-bug, test-bug,
etc.), it seems to me like 'external' would fit in. Then the bug
could be set to java/external/suspended, which I think would be a
useful classification.
David Carlton
carlton@math.stanford.edu
next reply other threads:[~2003-03-14 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 17:40 David Carlton [this message]
2003-03-31 5:51 ` Andrew Cagney
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=ro1wuj1j18t.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).