You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by Apache Wiki <wi...@apache.org> on 2011/10/31 16:39:11 UTC

[Subversion Wiki] Update of "BranchesAndBranchRoots" by JulianFoad

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

New page:
== Branch Names as Aliases for URLs ==

Here's a simple way in which Subversion could "know about" branches in a simplistic 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.

 * Branch names are to be unique within a codebase; codebase names are to be unique within a repository. Decide whether branch names and tag names should share the same namespace.

 * Introduce a command-line syntax for referring to { codebase-name, branch-name } instead of a URL (and with a relative URL); and for referring to { branch-name } in "this" codebase; and for referring to "this branch in this codebase".

 * Introduce the same or similar syntaxes for external definitions.

 * Introduce the same or similar syntaxes for viewspec files (svn-viewspec.py).

 * [...]


== Branches as First-Class Objects ==

Here's an attempt at defining the concept of "a branch" in terms of more advanced behaviour than simply substituting a URL into an existing subcommand.

[...]