From 6690079c456b9c0451abf3ab85e5294db721ceb6 Mon Sep 17 00:00:00 2001
From: Don HO <don.h@free.fr>
Date: Wed, 24 Jun 2015 13:45:12 +0200
Subject: [PATCH] [UPDATE] Change the guidelines

Remove the unnecessary guideline due to the new workflow.
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ebdebadbe..9a436d2c4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -25,7 +25,7 @@ bugs and enhancements before work begins, preventing wasted effort.
 2. Make a single change per commit.
 3. Make your modification compact - don't reformat source code in your request. It makes code review more difficult.
 4. PR of reformatting (changing of ws/TAB, line endings or coding style) of source code won't be accepted. Use issue trackers for your request instead.
-5. Only bug-fix and feature request will be accepted. For the other things, I can run static code analysis tool myself.
+
 
 In short: The easier the code review is, the better the chance your pull request will get accepted.