[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-commits
Subject:    svn commit: r1884689 - /subversion/trunk/notes/dump-load-format.txt
From:       esr () apache ! org
Date:       2020-12-22 5:11:15
Message-ID: 20201222051115.D866517A1F0 () svn01-us-east ! apache ! org
[Download RAW message or body]

Author: esr
Date: Tue Dec 22 05:11:15 2020
New Revision: 1884689

URL: http://svn.apache.org/viewvc?rev=1884689&view=rev
Log:
* notes/dump-load-format.txt
         Specify dump order. And describe special properties.


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=1884689&r1=1884688&r2=1884689&view=diff
 ==============================================================================
--- subversion/trunk/notes/dump-load-format.txt (original)
+++ subversion/trunk/notes/dump-load-format.txt Tue Dec 22 05:11:15 2020
@@ -1,6 +1,6 @@
 = How to interpret Subversion dumpfiles =
 
-Version 1.2, 2019-11-18
+Version 1.3, 2020-12-21
 
 == Introduction ==
 
@@ -97,6 +97,11 @@ that can parse RFC-822 messages.
 
 A revision record is followed by zero or more Node records (see below).
 
+Revisions are always dumped in monotonically increasing
+revision-number order. The date proprty of a revision may be
+explicitly set to any value, or even unset, but normally a sequence of
+commits will have monotonically increasing timestamps.
+
 ==== Node records ====
 
 Each Revision record is followed by one or more Node records.
@@ -368,6 +373,38 @@ to delete all properties from a path, th
 issue a node with an empty properties section. (This is different from
 an *absent* properties section, which will change no properties.)
 
+=== Special properties === 
+
+svn:author::
+    Identification of the commit author, normally a Unix username on
+    the repository server.
+
+svn:date::
+    An RFC3339 UTC timestamp to millisecond precision.  Here is an example:
+    "2011-11-30T16:41:55.154754Z". The length and precision of this
+    field is fixed: 27 characters with the trailing Zulu timezone
+    required.
+
+svn:log::
+    The change comment associated with this revision.
+
+The following per-node properties are interpreted by Subversion itself:
+
+svn:executable::
+    When this is set on a node, the executable bits in the metadata of
+    checkout copies corresponding file are set. On Unix systems which
+    of the x bits are set is filtered by the current umask.
+
+svn:ignore, svn:global-ignores::
+    Set ignore patterns for Subversion clients. Read the Subversion
+    manual for semantic details.
+
+svn:mergeinfo, svn:mime-type, svn:keywords, svn:eol-style, svn:externals::
+    Read the Subversion manual for semantic details.
+
+All other property settings are ignored by Subversion, but preserved
+in repositories and dump streams.
+
 === Representation of symbolic links ===
 
 When the Subversion client sends a content blob representing a
@@ -396,7 +433,7 @@ for each revision can be discarded after
 a source revision for a copyfrom, but there are cases in which doing
 this will leave you unable to trace ancestry chains through copies.
 
-Instead, is advisable to build your filemaps using a copy-on-write
+Instead, it is advisable to build your filemaps using a copy-on-write
 store.
 
 == An example ==


[prev in list] [next in list] [prev in thread] [next in thread]