summaryrefslogtreecommitdiff
path: root/README.Coding
diff options
context:
space:
mode:
authorDouglas Bagnall <douglas.bagnall@catalyst.net.nz>2018-03-23 15:12:06 +1300
committerAndrew Bartlett <abartlet@samba.org>2018-03-23 07:28:25 +0100
commit8ca43ec8e27bd4fabf9630b3f10cc0e4fcc04894 (patch)
tree42e74fe0cfc824c56b4389898a387781f7ddf835 /README.Coding
parentcd1136f39bba306419ef19c2c0884e694a59f2d0 (diff)
downloadsamba-8ca43ec8e27bd4fabf9630b3f10cc0e4fcc04894.tar.gz
README.Coding: remove reference to non-existent prog_guide4.txt
Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Diffstat (limited to 'README.Coding')
-rw-r--r--README.Coding8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.Coding b/README.Coding
index fc807ef0f7b..3d4c5a59e5d 100644
--- a/README.Coding
+++ b/README.Coding
@@ -16,10 +16,10 @@ style should never outweigh coding itself and so the guidelines
described here are hopefully easy enough to follow as they are very
common and supported by tools and editors.
-The basic style for C code, also mentioned in prog_guide4.txt, is the Linux kernel
-coding style (See Documentation/CodingStyle in the kernel source tree). This
-closely matches what most Samba developers use already anyways, with a few
-exceptions as mentioned below.
+The basic style for C code is the Linux kernel coding style (See
+Documentation/CodingStyle in the kernel source tree). This closely matches
+what most Samba developers use already anyways, with a few exceptions as
+mentioned below.
The coding style for Python code is documented in PEP8,
http://www.python.org/pep/pep8. New Python code should be compatible with