summaryrefslogtreecommitdiff
path: root/TAO/CIAO/PROBLEM-REPORT-FORM
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/CIAO/PROBLEM-REPORT-FORM')
-rw-r--r--TAO/CIAO/PROBLEM-REPORT-FORM34
1 files changed, 7 insertions, 27 deletions
diff --git a/TAO/CIAO/PROBLEM-REPORT-FORM b/TAO/CIAO/PROBLEM-REPORT-FORM
index 5cda35bc57e..4933c6e92ce 100644
--- a/TAO/CIAO/PROBLEM-REPORT-FORM
+++ b/TAO/CIAO/PROBLEM-REPORT-FORM
@@ -1,9 +1,7 @@
-[Please use the PRF form below to submit bug reports, problem
+[Please use the form below to submit bug reports, problem
reports, etc., to the CIAO developers and interested users.
- Send to ciao-users@cs.wustl.edu. If you are using OCI or PrismTech's
- versions of CIAO do not send bugs to this mailing list, but
- instead contact those companies for support. Please also send your
- PRF as plain ASCII text, _not_ uuencoded or as an attachment.
+ Send to ciao-users@cs.wustl.edu. Please send it as plain
+ ASCII text, _not_ uuencoded or as an attachment.
We prefer that all bug reports be submitted through our bug tracking
system. See $ACE_ROOT/docs/usage-bugzilla.html for more information
@@ -15,14 +13,11 @@
browse bugzilla and the ChangeLog files to find out if your problem
has been solved in a more recent version of CIAO.
- To ensure that you see responses, please do one of the following:
+ To ensure that you see responses, please try to subscribe to the
+ ciao-users mail list, by sending email with contents "subscribe
+ ciao-users" to majordomo@cs.wustl.edu.
- 1) Subscribe to the ciao-users mail list, by sending email with
- contents "subscribe ciao-users" to majordomo@cs.wustl.edu.
-
- 2) Or, monitor the comp.soft-sys.ace newsgroup for responses.
-
- Replace/remove all the explanatory text in brackets before mailing.
+ Replace/remove all the explanatory text in brackets before mailing.
Please send this form as ASCII text only. Do _not_ send it as an
attachment, or as tar'ed, compressed and/or uuencoded text. And
@@ -32,12 +27,6 @@
Subjects like "CIAO bug" or "bug report" are not helpful!
Also, do _not_ include the word "help" in the Subject!]
- When including your config.h and platform_macros.GNU files as requested
- below, only include the contents if you use the recommended method of
- including the platform-specific file in your file. If you use a link
- to the platform-specific file, simply state which one - DO NOT include
- an entire platform-specific configuration file in the form.
-
8<----------8<----------8<----------8<----------8<----------8<----------8<----
To: ciao-users@cs.wustl.edu
@@ -54,15 +43,6 @@ Subject: [area]: [synopsis]
TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
COMPILER NAME AND VERSION (AND PATCHLEVEL):
- CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a platform-
- specific file, simply state which one]:
-
- CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless
- this isn't used in this case, e.g., with Microsoft Visual C++):
-
- CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
- (used by MPC when you generate your own makefiles):
-
AREA/CLASS/EXAMPLE AFFECTED:
[What example failed? What module failed to compile?]