Repository Rules

We want good solutions for the problems. A good solution can be relative, but until one minute is acceptable. If your solution breaks the one-minute rule of project euler, the file solution can be pushed with one condition: use the suffix slow like solution_slow_1.xy. That way, the stats.py will not execute that.
Please update the STATUS.md in order for us to know what you are doing. That way we can attack more solutions in parallel.
CamelCase for folders and underscore for files. For each solution ensure using the layout of the example on final of this document.
On push if you get ! [rejected] master -> master (fetch first), PLEASE, don't create a useless fucking merge with git pull, instead this, execute git pull --rebase. The repository's history line will be glad with this.
Do not write solutions reading from stdin in any ways! That would make harder to generate a script for time measurement.
Optionally send PR with info about your processor and the time in which your solution takes to finish.
Add a md5sum hash of your solution on root of the Problem00x if no one exists yet.

Example

Problem00X/
..	Python/
	..	 solution_1.py
..	README.md
..      .hash

$ cat README.md
[The original source of problem](https://projecteuler.net/problem=29)

You can easily add a new template using the add script on the root of the repository. Just call:

./add <problem_num> <answer>