You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2011/07/08 22:28:56 UTC
svn commit: r1144494 - /subversion/trunk/subversion/libsvn_fs_fs/structure
Author: danielsh
Date: Fri Jul 8 20:28:56 2011
New Revision: 1144494
URL: http://svn.apache.org/viewvc?rev=1144494&view=rev
Log:
Merge another part of r1143964.
This still doesn't record it in mergeinfo since not all portions of that
revision have been merged.
* subversion/libsvn_fs_fs/structure:
Future-proof the "Filesystem formats" section.
Modified:
subversion/trunk/subversion/libsvn_fs_fs/structure
Modified: subversion/trunk/subversion/libsvn_fs_fs/structure
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_fs_fs/structure?rev=1144494&r1=1144493&r2=1144494&view=diff
==============================================================================
--- subversion/trunk/subversion/libsvn_fs_fs/structure (original)
+++ subversion/trunk/subversion/libsvn_fs_fs/structure Fri Jul 8 20:28:56 2011
@@ -139,39 +139,39 @@ The differences between the formats are:
Delta representation in revision files
Format 1: svndiff0 only
- Formats 2-5: svndiff0 or svndiff1
+ Formats 2+: svndiff0 or svndiff1
Format options
Formats 1-2: none permitted
- Format 3-5: "layout" option
+ Format 3+: "layout" option
Transaction name reuse
Formats 1-2: transaction names may be reused
- Format 3-5: transaction names generated using txn-current file
+ Format 3+: transaction names generated using txn-current file
Location of proto-rev file and its lock
Formats 1-2: transactions/<txnid>/rev and
transactions/<txnid>/rev-lock.
- Format 3-5: txn-protorevs/<txnid>.rev and
+ Format 3+: txn-protorevs/<txnid>.rev and
txn-protorevs/<txnid>.rev-lock.
Node-ID and copy-ID generation
Formats 1-2: Node-IDs and copy-IDs are guaranteed to form a
monotonically increasing base36 sequence using the "current"
file.
- Format 3-5: Node-IDs and copy-IDs use the new revision number to
+ Format 3+: Node-IDs and copy-IDs use the new revision number to
ensure uniqueness and the "current" file just contains the
youngest revision.
Mergeinfo metadata:
Format 1-2: minfo-here and minfo-count node-revision fields are not
stored. svn_fs_get_mergeinfo returns an error.
- Format 3-5: minfo-here and minfo-count node-revision fields are
+ Format 3+: minfo-here and minfo-count node-revision fields are
maintained. svn_fs_get_mergeinfo works.
Revision changed paths list:
Format 1-3: Does not contain the node's kind.
- Format 4-5: Contains the node's kind.
+ Format 4+: Contains the node's kind.
# Incomplete list. See SVN_FS_FS__MIN_*_FORMAT