subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Subversion Wiki] Update of "BranchesAndBranchRoots" by JulianFoad
Date Mon, 31 Oct 2011 15:43:11 GMT
Dear Wiki user,

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

The "BranchesAndBranchRoots" page has been changed by JulianFoad:
http://wiki.apache.org/subversion/BranchesAndBranchRoots?action=diff&rev1=1&rev2=2

  == Branch Names as Aliases for URLs ==
  
- Here's a simple way in which Subversion could "know about" branches in a simplistic way.
+ Subversion could "know about" branches in the following way.
  
   * Allow the user (or administrator) to configure a mapping between { codebase-name, branch-name
} and { path-within-repository }. For example, in the ASF repository, we might configure that
every path matching /subversion/trunk, /subversion/branches/* and /subversion/tags/* is to
be known as a "branch" in the "code base" named "subversion", and its branch name is the last
component of the pathname.
  
@@ -14, +14 @@

  
   * Introduce the same or similar syntaxes for viewspec files (svn-viewspec.py).
  
-  * [...]
+  * Introduce APIs for mapping (efficiently, of course) both ways - from names to the URL
of a branch root, and from an arbitrary URL to the codebase and branch names and the relative
URL within that branch.
+ 
+  * (more?)
+ 
+ This gives Subversion the ability to map between branch names and URLs, which is certainly
useful. This doesn't in itself cause any new or desirable behaviour with repect to merging
and other management of branches; by itself this is just syntactic sugar.
  
  
  == Branches as First-Class Objects ==

Mime
View raw message