You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ju...@apache.org on 2019/11/18 12:01:22 UTC

svn commit: r1869965 - /subversion/trunk/notes/dump-load-format.txt

Author: julianfoad
Date: Mon Nov 18 12:01:22 2019
New Revision: 1869965

URL: http://svn.apache.org/viewvc?rev=1869965&view=rev
Log:
* notes/dump-load-format.txt
  Clarifications about Prop-content-length and non-minimalism.

Modified:
    subversion/trunk/notes/dump-load-format.txt

Modified: subversion/trunk/notes/dump-load-format.txt
URL: http://svn.apache.org/viewvc/subversion/trunk/notes/dump-load-format.txt?rev=1869965&r1=1869964&r2=1869965&view=diff
==============================================================================
--- subversion/trunk/notes/dump-load-format.txt (original)
+++ subversion/trunk/notes/dump-load-format.txt Mon Nov 18 12:01:22 2019
@@ -151,6 +151,7 @@ Text-content-length will be present only
 Zero is a legal value for this length, indicating an empty file.
 
 Prop-content-length will be present only when there is a properties section.
+A properties section has non-zero length even if it has no entries.
 
 Content-length will be present if there is either a text or a
 properties section.  This is not always the case.  In particular, 
@@ -373,11 +374,6 @@ simply issue a node with an empty proper
 is different from an *absent* properties section, which will change
 no properties and will be associated with a change to content!
 
-Dumpfile generation is not minimalist about generating property
-sections. Interpreters should be prepared to see many empty property
-sections (nominally deleting all properties) when there are no
-previous properties set to be deleted.
-
 === Representation of symbolic links ===
 
 When the Subversion client sends a content blob representing a
@@ -390,6 +386,11 @@ be defined.  None such yet exist as of r
 
 === Implementation pragmatics ===
 
+Dumpfile generation in general is not canonical, nor minimalist. In
+particular, interpreters should be prepared to see many empty property
+sections (nominally deleting all properties) when there are no
+previous properties set to be deleted.
+
 Because directory operations with copyfroms don't specify all the file
 paths they modify, an interpreter for this format must build a map of
 the paths in the file store it is manipulating, and update that map as