On Mittwoch, 4. Juli 2007, Branko Čibej wrote:
...
> > I think that part of the reason why this feature might be important in
> > Subversion is that Subversion insists on *not* having a built-in
> > concept of "project", "branch" or "tag", or IOW to expose its
> > versioned-filesystem guts up to the command line client.
>
> Now that is one thing I'd like to get rid of. It turns out that in real
> life, in large projects, conflating the concepts of branches and
> directories is a PITA. Of course the /implementation/ of branches and
> directories is similar, but the semantics (and therefore user interface)
> is different.
To this I'd like to mention that the *technical* aspect of "just a directory
structure" is one of the most valuable design choices in subversion (IMHO, at
least).
Please don't change that.
If there are simply a few commands "svn branch", "svn tag" etc., which use
some properties at the repository root to know whether the structure is
/project/{trunk,branches,tags}
or
/{branches,tags,trunk}/project1,
the user interface can be done in any thinkable way.
But please keep the *basic* structure clean and simple.
(Probably I just misunderstood and worry too much, and the structure will
never change anyway.)
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 4 13:38:28 2007