From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: why do we set prms_id/bug_id in GDB testcases?
Date: Mon, 26 Apr 2010 19:00:00 -0000 [thread overview]
Message-ID: <m31ve2nipm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100426170109.GE2732@adacore.com> (Joel Brobecker's message of "Mon, 26 Apr 2010 13:01:09 -0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> On rare occcasions, we'll even set an actual PR number, which I
Joel> assume is the Mozilla PR number. Does this actually do anything?
It may print something to the log.
Joel> Maybe it's used internally by dejagnu? (I couldn't find evidence of that
Joel> in the dejagnu manual)
There are some references in the dejagnu .exp files, but I didn't
examine them closely.
I don't think it is extremely valuable to set these variables.
Maybe they provide some small documentation value. I've generally been
ignoring them in favor of a bug reference in the ChangeLog.
Tom
next prev parent reply other threads:[~2010-04-26 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 17:01 Joel Brobecker
2010-04-26 19:00 ` Tom Tromey [this message]
2010-04-26 19:09 ` Stan Shebs
2010-04-26 22:11 ` Joel Brobecker
2010-05-05 18:14 ` Joel Brobecker
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=m31ve2nipm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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