selftest: enable py3 for samba.tests.dcerpc.rpc_talloc

[metze/samba/wip.git] / README.Coding

diff --git a/README.Coding b/README.Coding
index fc807ef0f7b98f0331be9116d163a7fe4f9bde46..3d4c5a59e5d191bbe545ec116b938dee5710b257 100644 (file)
--- 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