subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache subversion Wiki <comm...@subversion.apache.org>
Subject [Subversion Wiki] Update of "InheritedProperties" by pburba
Date Tue, 31 Jan 2012 15:56:28 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.

The "InheritedProperties" page has been changed by pburba:
http://wiki.apache.org/subversion/InheritedProperties?action=diff&rev1=9&rev2=10

Comment:
Remove "svn:i:" examples and replace with "svn:inheritable:"

    [danielsh] Using the 'svn:inheritable:' namespace precludes a property from being both
inheritable and ${some_future_semantics}, since a property name cannot be simultaneously in
the 'svn:inheritable:' namespace and in the 'svn:{some_future_semantics}:' namespace.
  }}}
  == Inheritance Rules ==
- Inheritance will be very similar to the current svn:mergeinfo inheritance model.  For a
given inheritable property 'svn:i:X':
+ Inheritance will be very similar to the current svn:mergeinfo inheritance model.  For a
given inheritable property 'svn:inheritable:X':
  
-  1. A path '''''with''''' svn:i:X' explicitly set on it never inherits that property (i.e.
a path can only inherit a property it doesn't have set on itself).''''' '''''
+  1. A path '''''with''''' svn:inheritable:X' explicitly set on it never inherits that property
(i.e. a path can only inherit a property it doesn't have set on itself).''''' '''''
-  1. A repository path@REV '''''without''''' the 'svn:i:X' property explicitly set on it
(we'll refer to this as the 'child' path from here on) may inherit the property from the path's
nearest path-wise ancestor@REV with the 'svn:i:X' property explicitly set on it (we'll refer
to this as the 'parent' path).
+  1. A repository path@REV '''''without''''' the 'svn:inheritable:X' property explicitly
set on it (we'll refer to this as the 'child' path from here on) may inherit the property
from the path's nearest path-wise ancestor@REV with the 'svn:inheritable:X' property explicitly
set on it (we'll refer to this as the 'parent' path).
-  1. A '''''working copy''''' child path '''''without''''' the 'svn:i:X' property explicitly
set on it may inherit the property from the path's nearest path-wise ancestor in the working
copy.
+  1. A '''''working copy''''' child path '''''without''''' the 'svn:inheritable:X' property
explicitly set on it may inherit the property from the path's nearest path-wise ancestor in
the working copy.
    * For working copies with no switched subtrees, this inheritance can occur from any parent
path up to the root of the working copy.
    * If the path is located within a switched subtree then the inheritance can occur up to
the root of the switched subtree.
    * Unlike svn:mergeinfo and like tsvn:auto-props, inheritance across mixed-revision boundaries
in the working copy is allowed.
-   * If a working copy child path doesn't find a parent with 'svn:i:X' that it can inherit
from before it reaches the working copy (or switched subtree) root, then it may inherit the
property from the inherited properties cache (see below).
+   * If a working copy child path doesn't find a parent with 'svn:inheritable:X' that it
can inherit from before it reaches the working copy (or switched subtree) root, then it may
inherit the property from the inherited properties cache (see below).
    {{{#!wiki note
      [JAF] What is the unifying principle behind the set of rules?  For example, a principle
could be:<<BR>>
      "Inheritance within a WC is based on inheritance within a single revision of the tree
structure.  Thus, a WC base node inherits from its repository parent in its repository revision,
no matter whether that is present in the WC.  The working version of the WC tree is treated
as a single revision: an as yet unnumbered prototype for a revision that might be committed
into the repository (or might not)[1].  Thus, a WC working node[2] inherits from the parent
node that it would have in the repository if the current WC were committed in full."<<BR>>

Mime
View raw message