Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-1505

cvs2svn needs to handle unlabeled branches better

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Duplicate
    • Affects Version/s: all
    • Fix Version/s: cvs2svn-1.0
    • Component/s: tools
    • Labels:
      None

      Description

      If an RCS repository is coerced into the directory layout of a CVS
      repository and subsequently converted using cvs2svn, cvs2svn may
      select incorrect file versions in the presence of RCS branches.
      
      Apparently cvs2svn places file versions on /trunk in their
      chronological order, without regards to which RCS branch they appeared
      in, unless there exists a corresponding CVS branch label, in which case 
      it seems to work.
      
      RCS lacks the concept of branch labels, but if the original RCS files
      are manually edited to define such labels, the cvs2svn conversion 
      proceeds
      without errors, as far as I have seen.
      
      This issue proposes therefore that:
      * revisions on RCS branches not corresponding to a CVS branch label 
      should be disregarded, and/or
      * a warning should be written to the user if such a revision is 
      encountered.
      
      Mailing list threads:
      http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=1109
      
      http://www.contactor.se/~dast/svnusers/archive-2003-08/0879.shtml
      http://www.contactor.se/~dast/svnusers/archive-2003-09/0005.shtml
      

      Original issue reported by pommac2

        Attachments

        1. 1_1505-fix.patch
          0.9 kB
          Max Oliver Bowsher
        2. 2_t.txt
          0.7 kB
          Max Oliver Bowsher
        3. 3_cvsbehavior.sh
          1 kB
          Karl Fogel

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                subversion-importer Subversion Importer
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: