On 8/23/05, Michael Tiller <email@example.com> wrote:
> 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.
What do you see as 'natural'? The CVS way?
> 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.
I guess you want a new command 'branch' which then only takes a *name*
(not an URL) and TSVN would do the rest automatically.
It isn't really clear why and what you want here, so I'm just guessing.
> 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.
Why is branching/tagging confusing? Take for example people who have
*never* used version control before. When those people make a
'release', they select the folder with their data and copy that folder
to another place, and then rename that folder to e.g. 'release 1.0'.
That's exactly what you do in Subversion: you create a copy of the
folder you're working on (trunk) in the place where you store all the
> 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
If you can find a way which will work *reliably* (that means there are
no special cases where it wouldn't work or even worse do something
completely unexpected) then we definitely will consider your proposal.
But be warned: many people have tried before, and we always found some
edge case where it wouldn't work.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Aug 25 19:52:46 2005