diff options
| author | Tomi Ollila <tomi.ollila@iki.fi> | 2011-09-12 08:59:09 +0300 |
|---|---|---|
| committer | Tomi Ollila <tomi.ollila@iki.fi> | 2011-09-12 08:59:09 +0300 |
| commit | 889266d3dfcd3f478978cf136a94f3448696999a (patch) | |
| tree | 8a940254f2562817530a47225c83adc6457919d2 /patchformatting.mdwn | |
| parent | 99d2deb20edb3e7633bf319200d54a2b5f984407 (diff) | |
removed note "(in any particular project)";
inconsistent here, could be described more generally for the whole section.
Diffstat (limited to 'patchformatting.mdwn')
| -rw-r--r-- | patchformatting.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/patchformatting.mdwn b/patchformatting.mdwn index 9f92423..cf5bf81 100644 --- a/patchformatting.mdwn +++ b/patchformatting.mdwn @@ -10,7 +10,7 @@ you should check the following: 2. Read mailing list (archives) and follow the discussions on the patches sent. -3. Get familiar with coding conventions used (in any particular project). +3. Get familiar with coding conventions used. This way you get some insight of the look and feel of the patches sent, both the way code should be written, how to write commit log messages |