Author: gd
Date: 2004-12-02 12:19:54 +0000 (Thu, 02 Dec 2004)
New Revision: 294

WebSVN: 
http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-docs&rev=294

Log:
"mangle case" silently vanished with samba 3.0.6. Reflect this fact
in the docs. Thanks to Bjoern Jacke.

Guenther

Removed:
   trunk/smbdotconf/filename/manglecase.xml
Modified:
   trunk/manpages/smb.conf.5.xml


Changeset:
Modified: trunk/manpages/smb.conf.5.xml
===================================================================
--- trunk/manpages/smb.conf.5.xml       2004-11-25 00:36:07 UTC (rev 293)
+++ trunk/manpages/smb.conf.5.xml       2004-12-02 12:19:54 UTC (rev 294)
@@ -483,14 +483,6 @@
        <variablelist>
        
        <varlistentry>
-               <term>mangle case = yes/no</term>
-               <listitem><para> controls whether names that have characters 
that 
-               aren't of the <quote>default</quote> case are mangled. For 
example, 
-               if this is yes, a name like <quote>Mail</quote> will be 
mangled. 
-               Default <emphasis>no</emphasis>.</para></listitem>
-               </varlistentry> 
-       
-               <varlistentry>
                <term>case sensitive = yes/no/auto</term>
                <listitem><para>controls whether filenames are case sensitive. 
If 
                they aren't, Samba must do a filename search and match on 
passed 

Deleted: trunk/smbdotconf/filename/manglecase.xml
===================================================================
--- trunk/smbdotconf/filename/manglecase.xml    2004-11-25 00:36:07 UTC (rev 
293)
+++ trunk/smbdotconf/filename/manglecase.xml    2004-12-02 12:19:54 UTC (rev 
294)
@@ -1,9 +0,0 @@
-<samba:parameter name="mangle case"
-                 context="S"
-                                type="boolean"
-                 xmlns:samba="http://samba.org/common";>
-<description>
-       <para>See the section on <link linkend="NAMEMANGLINGSECT">NAME 
MANGLING</link></para>
-</description>
-<value type="default">no</value>
-</samba:parameter>

Reply via email to