Re: Restructuring svn

2009-06-12 Thread Mladen Turk
+1 Mark Thomas wrote: Once 4.1.x is archived, there will be no release branches sharing code. We could also pull out mod_jk and tcnative along the lines of /repos/asf/tomcat /mod_jk /tcnative Finally! :) Regards -- ^(TM)

Restructuring svn

2009-06-10 Thread Mark Thomas
Once 4.1.x is archived, there will be no release branches sharing code. Therefore, we have the option to restructure 5.5.x to remove the use of externals. This would remove /repos/asf/tomcat /build /container /connector /current /current-svn15 /jasper /servletapi and replace them

Re: Restructuring svn

2009-06-10 Thread Yoav Shapira
On Wed, Jun 10, 2009 at 10:48 AM, Mark Thomasma...@apache.org wrote: Once 4.1.x is archived, there will be no release branches sharing code. Therefore, we have the option to restructure 5.5.x to remove the use of +1. Yoav -

Re: Restructuring svn

2009-06-10 Thread Henri Gomez
+1 also 2009/6/10 Yoav Shapira yo...@apache.org: On Wed, Jun 10, 2009 at 10:48 AM, Mark Thomasma...@apache.org wrote: Once 4.1.x is archived, there will be no release branches sharing code. Therefore, we have the option to restructure 5.5.x to remove the use of +1. Yoav

Re: Restructuring svn

2009-06-10 Thread Filip Hanik - Dev Lists
+1 Filip Mark Thomas wrote: Once 4.1.x is archived, there will be no release branches sharing code. Therefore, we have the option to restructure 5.5.x to remove the use of externals. This would remove /repos/asf/tomcat /build /container /connector /current /current-svn15 /jasper