It is now the turn of the servletapi repositories.

Given the previously expressed views on how these might be better named and my experience of the migration process so far I have modified my plan for servletapi part of the repository. The new version is at the end of this mail.

Changes are:
- Restructured the 'other' dirs so tags and branches remained separate
- Used combination of spec and Tomcat version for dir names
- Renamed 'trunk' using the same naming convention

I will be placing this request with infra shortly but there is time to modify this structure if needs be.

Mark


Directory          CVS Module(s)              CVS Branch/Tag
--------------     --------------------       --------------
/tomcat/
  /servletapi/
    /servlet2.4-jsp2.0-tc5.x/
                   j-servletapi-5             HEAD
    /branches/
      /servlet2.2-jsp1.1-tc3.x/
                   j-servletapi               HEAD
      /servlet2.3-jsp1.2-tc4.x/
                   j-servletapi-4             HEAD
      /other/
        /servlet2.2-jsp1.1-tc3.x/
                   j-servletapi               All other branches
        /servlet2.3-jsp1.2-tc4.x/
                   j-servletapi-4             All other branches
        /servlet2.4-jsp2.0-tc5.x/
                   j-servletapi-5             All other branches
    /tags/
      /servlet2.2-jsp1.1-tc3.x/
                   j-servletapi               All 4.x tags
      /servlet2.3-jsp1.2-tc4.x/
                   j-servletapi-4             All 3.x tags
      /servlet2.4-jsp2.0-tc5.x/
                   j-servletapi-5             All 5.x tags
      /other/
        /servlet2.2-jsp1.1-tc3.x/
                   j-servletapi               All other tags
        /servlet2.3-jsp1.2-tc4.x/
                   j-servletapi-4             All other tags
        /servlet2.4-jsp2.0-tc5.x/
                   j-servletapi-5             All other tags


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to