From f28539265d753bbaa473cb488e951bfe47304a01 Mon Sep 17 00:00:00 2001
From: Rickard Green <rickard@erlang.org>
Date: Thu, 12 Oct 2017 16:28:31 +0200
Subject: Revert "Merge branch 'rickard/null-char-filenames/ERL-370/OTP-14543'
 into maint"

This reverts commit 0717a2194e863f3a78595184ccc5637697f03353, reversing
changes made to 71a40658a0cef8b3e25df3a8e48a72d0563a89bf.
---
 lib/stdlib/doc/src/filelib.xml | 24 ------------------------
 1 file changed, 24 deletions(-)

(limited to 'lib/stdlib/doc/src/filelib.xml')

diff --git a/lib/stdlib/doc/src/filelib.xml b/lib/stdlib/doc/src/filelib.xml
index 57c4348745..80c4acffdb 100644
--- a/lib/stdlib/doc/src/filelib.xml
+++ b/lib/stdlib/doc/src/filelib.xml
@@ -45,30 +45,6 @@
 
     <p>For more information about raw filenames, see the
       <seealso marker="kernel:file"><c>file</c></seealso> module.</p>
-
-    <note>
-      <p>
-	Functionality in this module generally assumes valid input and
-	does not necessarily fail on input that does not use a valid
-	encoding. You can validate the encoding of a filename using
-	<seealso marker="stdlib:filename#validate/1">filename:validate/1</seealso>.
-      </p>
-      <p>
-	File operations used to accept filenames containing
-	null characters (integer value zero). This caused
-	the name to be truncated at the first null character.
-	Filenames containing null characters inside the filename
-	are now <em>rejected</em> and will cause primitive
-	file operations fail.
-      </p>
-    </note>
-    <warning><p>
-      Currently null characters at the end of the filename
-      will be accepted by primitive file operations. Such
-      filenames are however still documented as invalid. The
-      implementation will also change in the future and
-      reject such filenames.
-    </p></warning>
   </description>
 
   <datatypes>
-- 
cgit v1.2.3