> Before we start looking at that route, have you found the repository
> browser yet? This gives an explorer-like view of the repo structure so
> you can see what naming conventions are already in use by a given
> repository. Most places you need to use this sort of URL, like in the
> branch/tag dialog, the browse button takes you straight into the repo
> browser. Also, once you have browsed to an existing URL, you can copy
> the URL and paste it somewhere else.
OK first I want to restate, in case it wasn't already obvious, that I think
that the Tortoise* tools are great and I appreciate all the steps that have
been taken so far to make version control as natural as possible.
The browser is really nice and for me it is just fine. But, what I'm
looking for is something that will allow me to transparently enforce certain
policies without having to explain them to the users. By providing an a
priori specification for the repository layout, I avoid the entire issue of
having to explain how Subversion does branching and what particular branch
structure we use.
This just struck me as a way to encapsulate, on an opt-in basis, the policy
and branching details in a way that would make version control more
acceptable to those people who already find it confusing by reducing the
entire notion of branch and tag back down to a simple identifier.
It occurs to me that a slightly richer set of patterns will be required
(e.g. what if the repository contains several projects, each with their own
branches). I'll be more than happy to refine this proposal if people are
interested but I just wanted to gauge the general acceptance of the concept
first.
> Simon
--
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Aug 23 16:28:04 2005