@omlk if you do not follow the correct process then your changes will go into the bit bucket.
As you seem to not want to follow the correct process here it is AGAIN:
1) Make sure your changes are against the truck SVN or github sources. OR in other words get the latest source code before you post any patches the same day you are going to submit the patch(s) and if there are any updated merge your changes into the latest code and test the changes are still working and okay.
2) Create a proper patch file, not a zip file containing files usign one of the following :
a) Read
http://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker) to follow the CB process
or
b) Google "gnu create a patch file" and read how to create a patch file using the standard GNU diff utility if you have a GNU diff installed.
or
c) Use Github to create a pull request against. See previous past that has GIT repo to fork from in it (
https://github.com/obfuscated/codeblocks_sf)
3) Create a ticket on SourceForge (
https://sourceforge.net/p/codeblocks/tickets/)
4) Attach the patch to the ticket from 3) or include the Github PR URL in the ticket if you used GitHUB.
If you still want to ignore this and submit a zip file containing the files you have changed then you are wasting real CB developers time.
