Review destination branch/tag names

[dabrahams]

Some examples of issues that should be considered:

• We have lots of refs beginning with old-branches/. I believe that name was chosen originally by @jwiegley because either the branch had been deleted (in which case we can let svn2git handle that using its backups/ feature) or because it is not being actively developed. IIRC in that case he was directing the old branch at a tag, which we are not currently doing.
• there are lots of duplicate ref name suffixes in SVN, some of which are being collapsed to the same tag in git. This mostly happens in the Boost.Build repo, where we have, e.g., /tags/jam/ and /tags/tools/jam/<whatever>. It seems likely that these tags were all simply moved/re-rooted... ah, yes, see r39733. In a case like that, the collapsing is fine, but we should try to be sure of it.

[purpleKarrot]

• Agreed. I don't like the old-branches/ prefix either.
• Yes. It would be nice if we cleaned up the history. Instead of creating a banch and later renaming it, the final name can be set directly. Commits like r39733 then don't have to be reflected at all in git.

[dabrahams]

I don't exactly dislike old-branches/, but I'm not sure it's still relevant. You realize that deleted things will get a backups/ prefix unless we do something about that, right?