diff options
author | Dieter Plaetinck <dieter@plaetinck.be> | 2009-05-17 00:13:10 +0200 |
---|---|---|
committer | Dieter Plaetinck <dieter@plaetinck.be> | 2009-05-17 00:13:10 +0200 |
commit | 8d0abbb767e5023f5824dacf18c527d156b6cdac (patch) | |
tree | ba263c4c19b5c4be5bf8a6dfff9955a52a74b840 /docs/CONTRIBUTING | |
parent | 7173758a6cb22ae351a97eb49212f84006124e09 (diff) |
todos/docs cleanup
Diffstat (limited to 'docs/CONTRIBUTING')
-rw-r--r-- | docs/CONTRIBUTING | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/CONTRIBUTING b/docs/CONTRIBUTING index bd733a9..196cda4 100644 --- a/docs/CONTRIBUTING +++ b/docs/CONTRIBUTING @@ -15,7 +15,10 @@ code and clone the code to start hacking. (github makes this really easy with their "fork" concept). But it's usually a good thing to tell us first what you want to do, to avoid unneeded or duplicate work. - +Note that cloning and letting us pull (preferably via github) is way more +workable then submitting plain patches. Git is good in merging in branches +even if the base code has changed in the meanwhile. This does not work with +patches. ### VALGRIND PROFILING $ add this to Makefile header: CFLAGS=-g |