Skip to content
GitLab
Menu
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
TASTE
Ocarina
Commits
12b61011
Commit
12b61011
authored
Dec 30, 2016
by
yoogx
Browse files
* Remove deprecated file
For issue #81
parent
cf7533b5
Changes
1
Show whitespace changes
Inline
Side-by-side
doc/PROBLEM-REPORT-FORM
deleted
100644 → 0
View file @
cf7533b5
This template lists all relevant information required by Ocarina
developpers to process your bug report.
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
limit line lengths to less than 80 characters.
PLEASE make your Subject: line as descriptive as possible.
Subjects like "Ocarina bug" or "bug report" are not helpful!
8<----------8<----------8<----------8<----------8<----------8<----------8<----
OCARINA VERSION:
[Please provide the complete output of "ocarina -V".]
HOST MACHINE and OPERATING SYSTEM:
COMPILER VERSION
[Please provide the complete version string from "gnatls -v" if you
try to compile Ocarina or PolyORB-HI/Ada, or "gcc --version" for
PolyORB-HI/C.]
[Note: if you build from the repository, please also include autoconf
and automake versions: "autoconf --version", "automake --version"]
DESCRIPTION:
[Detailed description of problem. Don't just say "<blah>
doesn't work, here's a fix," explain what your program does
to get to the <blah> state. ]
REPEAT BY:
[What you did to get the error; include test program or session
transcript if at all possible; detail your application topology if it
uses several nodes, and describe the expected results; include the
configuration file you use, after stripping all comments; include all
information regarding any other middleware you use. ]
SAMPLE FIX/WORKAROUND:
[If available]
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment