[svnbook commit] r2955 - trunk/src/en/book
cmpilato
noreply at red-bean.com
Fri Dec 28 12:33:09 CST 2007
Author: cmpilato
Date: Fri Dec 28 12:33:06 2007
New Revision: 2955
Log:
* src/en/book/ch03-advanced-topics.xml
Add some notes about how binariness effects property setting.
Modified:
trunk/src/en/book/ch03-advanced-topics.xml
Modified: trunk/src/en/book/ch03-advanced-topics.xml
==============================================================================
--- trunk/src/en/book/ch03-advanced-topics.xml (original)
+++ trunk/src/en/book/ch03-advanced-topics.xml Fri Dec 28 12:33:06 2007
@@ -965,6 +965,29 @@
attempts at performing contextual merges on files that simply
cannot be contextually merged.</para>
+ <warning>
+ <para>The <literal>svn:mime-type</literal> property, when set
+ to a value that does not indicate textual file contents, can
+ cause some unexpected behaviors with respect to other
+ properties. For example, since the idea of line endings
+ (and therefore, line ending conversion) makes no sense when
+ applied to non-textual files, Subversion will prevent you
+ from setting the <literal>svn:eol-style</literal> property
+ on such files. This is obvious when attempted on a single
+ file target—<command>svn propset</command> will error
+ out. But it might not be as clear if you perform a
+ recursive property set, where Subversion will silently skip
+ over files which it deems unsuitable for a given
+ property.</para>
+ </warning>
+
+ <para>Beginning in Subversion 1.5, users can configure a new
+ <literal>mime-types-file</literal> runtime configuration
+ parameter, which identifies the location of a MIME types
+ mapping file. Subversion will consult this mapping file to
+ determine, for newly added and imported files, their MIME
+ type.</para>
+
<para>Also, if the <literal>svn:mime-type</literal> property is
set, then the Subversion Apache module will use its value to
populate the <literal>Content-type:</literal> HTTP header when
More information about the svnbook-dev
mailing list