Hi,
aside from the "clean" layout argument, is there any known performance issue
when using extra folders organization in SVN ?
Does the level where the branches/tags/trunk folder is located has any
importance, as long as it is consistent with each project's architecture ?
Having read that they were optional, I would doubt so.
I really don't want to enter "religious" discussions about repositories
layouts, but wouldn't it be a better idea to leave that choice to the
end-user who might (as I am) be constrained to certain infrastructure
concerns, while giving the most features possible so as to make the job
easier ?
You also refer to repository creation, but for instance I'm actually
migrating existing projects from another SCS, which doesn't quite let me the
freedom to refactor every project, to "clean" them...
I think I might not be alone in that case.
Anyhow, your help was greatly appreciated, thank you again for that nice
tool,
have a nice day,
--Peter.
On 4/25/06, Stefan Küng <tortoisesvn@gmail.com> wrote:
>
> Peter Scmsvn wrote:
> > As a Followup,
> >
> > could the possibility to select multiple folders in the repo-browser,
> > and check them out in the current folder (creating the subfolders
> > automatically) be implemented in future revisions ?
>
> No, sorry.
> We don't want to make it easier for users to create nested layouts. We'd
> rather encourage them to create clean repository layouts.
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
Received on Tue Apr 25 22:56:10 2006