I generally don't like deep file hierarchies as they tend to bury
things, but since we do have one subproject already I think an
organization like Two has some long-term advantages.
On 5/11/10 6:30 AM, Benson Margulies wrote:
Two alternatives.
One, ignore me. We'll end up like CXF, which looks like:
cxf/
trunk
tags
branches
sandboxes
dosgi
web
osgi
in other words, the subproject top-levels and such are just sitting
there next to the main project's trunk/tag/branches. That gave me an
itch, thus ....
Two, which was my original idea:
mahout/
code/
mahout/
trunk,tags,branches
collections/
trunk,tag,branches
something-else-next-week/
trunk,tag,branches
sandboxes
web
So the current top would become repos/mahout/code/mahout
On Tue, May 11, 2010 at 9:22 AM, Grant Ingersoll<[email protected]> wrote:
On May 11, 2010, at 9:20 AM, Benson Margulies wrote:
Grant, just to be tiresome, I'll remind you that relocating the
existing mahout svn root down a directory level will reduce the effort
level of the later introductions of subprojects, sandboxes, etc.
What's the structure that you propose?
We have now:
/mahout
/trunk
/tags/
/branches
/pmc
