diff options
| author |  Dieter Plaetinck <dieter@plaetinck.be> | 2009-07-15 22:12:10 +0200 |
|---|---|---|
| committer | Dieter Plaetinck <dieter@plaetinck.be> | 2009-07-15 22:12:10 +0200 |
| commit | f8cffd77d5cd734389fb11966c9eb90315e8c8ed (patch) | |
| tree | ca6db3e2d625eeebd58a5fce09033998c5d55ffe /docs/CONTRIBUTING | |
| parent | 42c87fb308831265bc7571bed23c47015ac9c29e (diff) | |
| parent | 23edd78c1d0f1f370bdaa837aad2d77fec2625bf (diff) | |
Merge commit 'holizz/whitespace' into experimental
Diffstat (limited to 'docs/CONTRIBUTING')
| -rw-r--r-- | docs/CONTRIBUTING | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/CONTRIBUTING b/docs/CONTRIBUTING index f5d7ebc..c26e49a 100644 --- a/docs/CONTRIBUTING +++ b/docs/CONTRIBUTING @@ -66,6 +66,9 @@ This is a relatively easy, solid and transparent way to handle all requests in o we know for bigger changes this is not always feasible. Just try to keep the merges about bigger "clean changesets". * Your code should not introduce any compile warnings or errors. And also, no regressions but that's harder to check. +* Please try to keep the code clean - we don't like extraneous whitespace. + The sample pre-commit hook can check for this - so go ahead and + $ cp .git/hooks/pre-commit.sample .git/hooks/pre-commit That said, you can always ask us to check on your stuff or ask for advice. |