I agree. The repository that I'm interested in converting has branches all over the place /sandbox/, /sandbox/<username>/*, /stable/MAIN/*, /stable/Features/*, /features/*, /branches/*, etc... Because subversion didn't enforce the convention it was all to easy to ignore when our questionable branching strategy was created. Instead of expecting sub-folders of a particular path to be a branch is there something that we can key off of in the dumpfile? Are copy operations notated in some fashion? > Subversion uses the inter-file branching model (Wikipedia says it was > "borrowed" from Perforce) to handle branches and tags. ÂIt uses "branches > are copies (folders)" paradigm, and technically it doesn't have separate > namespace for branches but have projects, branches, and projects' > filesystem hierarchy mixed together; what part of path is branch name > is defined by convention only. ÂThis model makes it easy to mess up > repository (because there are no technological barriers for going > against conventions, like mentioned all-branches change, or changing > tags, or reversed hierarchy or branches and projects). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html