Re: CVSROOT type functionality?

Hello Robert!

> True. This reflects what feels like an odd overload to me. It would
> seem more natural to me to have svn commands act on working directories
> (always), and reserve all direct repo actions for svnadmin (for that
> well deserved extra dose of respect). That seems more intuitive to me
> than having some commands have "direct commit" semantics. But that's
> probably not going to be considered at this point in the game.

It may seem strange if you're talking about simple commands in your
working copy. But think about something like that: you have a repository
where your trunk/ directory has about 50MB (a huge project) and you have
dozens of developers working on 30 different branches of development,
and 100 tags were already made. How do you add or remove a new branch?
Are you going to checkout your whole repository ((1+30+100)*50 == 6.55GB)
to add or remove a branch? The way it was implemented looks wonderful
to me.

-- 
Gustavo Niemeyer
[ 2AAC 7928 0FBF 0299 5EB5  60E2 2253 B29A 6664 3A0C ]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org