[Bug 3529] New: Detect multi-step SVN branch creation

[bugzilla-daemon at bz.selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3529

          Priority: normal
            Bug ID: 3529
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Detect multi-step SVN branch creation
          Severity: feature
    Classification: Unclassified
                OS: All
          Reporter: cowwoc at bbs.darktech.org
          Hardware: All
            Status: UNCONFIRMED
           Version: 2.2.1
         Component: convert
           Product: Mercurial

I just discovered an edge case that leads the convert plugin to create
"floating branches" without a connection to the "default" branch. To be honest,
this is probably a case of user error. The authors did not adhere to the
standard directory structure but "svn.branches" cannot be used to fix it so I
thought I'd bring it up.

If you convert http://gstreamer-java.googlecode.com/svn to Mercurial you will
notice two floating branches that don't fork off the "default" branch:
"gstreamer-java" and "1.4-maven"

In both these cases, someone issued:

svn add /branches/foo, followed by
svn copy /trunk /branches/foo/bar

The plugin might be getting thrown off by two factors:

1. The branch is created using "svn add" instead of "svn copy"
2. The branch is created as a subdirectory of "foo"

Is it possible to improve handling for this use-case or should we just not
bother?

NOTE: I don't own the gstreamer-java repository. I'm just an end-user.

-- 
You are receiving this mail because:
You are on the CC list for the bug.