Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
Frama-C Website
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
Frama-C Website
Compare revisions
1c5ff9fae148047e5bec64c35f86d85fb8b1408a to c927e7f687e23669cb5b8b4d49a5f19787727ecc
Compare revisions
Changes are shown as if the
source
revision was being merged into the
target
revision.
Learn more about comparing revisions.
Source
pub/pub.frama-c.com
Select target project
No results found
c927e7f687e23669cb5b8b4d49a5f19787727ecc
Select Git revision
Swap
Target
pub/pub.frama-c.com
Select target project
pub/pub.frama-c.com
1 result
1c5ff9fae148047e5bec64c35f86d85fb8b1408a
Select Git revision
Show changes
Only incoming changes from source
Include changes to target since source was created
Compare
Commits on Source (2)
Less aggressive reporting guidelines
· 0f406185
Allan Blanchard
authored
4 years ago
0f406185
Merge branch 'content/blanchard/bug-reporting-less-aggressive' into 'master'
· c927e7f6
Andre Maroneze
authored
4 years ago
Less aggressive reporting guidelines See merge request
!31
c927e7f6
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
dokuwiki/bug_reporting_guidelines.md
+2
-3
2 additions, 3 deletions
dokuwiki/bug_reporting_guidelines.md
with
2 additions
and
3 deletions
dokuwiki/bug_reporting_guidelines.md
View file @
c927e7f6
...
@@ -26,10 +26,9 @@ Some advices to post your issue:
...
@@ -26,10 +26,9 @@ Some advices to post your issue:
-
If the bug report is not for a crash, include the
**
EXPECTED
-
If the bug report is not for a crash, include the
**
EXPECTED
BEHAVIOR
**
that you would have liked to see.
BEHAVIOR
**
that you would have liked to see.
-
Include the
**OBTAINED BEHAVIOR**
in enough detail that someone else
-
Include the
**OBTAINED BEHAVIOR**
in enough detail that someone else
(smart, but not mind-reading) can decide if they have reproduced
can decide if they have reproduced your bug.
your bug.
-
Include
**HOW TO REPRODUCE**
the issue. Provide everything necessary
-
Include
**HOW TO REPRODUCE**
the issue. Provide everything necessary
for
a smart, but not mind-reading, human
to reproduce the bug: input
for
someone else
to reproduce the bug: input
files, command line used, sequence of actions. If your analysis
files, command line used, sequence of actions. If your analysis
project depends on system headers, please use one of the two following
project depends on system headers, please use one of the two following
options to be sure that:
options to be sure that:
...
...
This diff is collapsed.
Click to expand it.