This reverts commit de7478f43f.
We've noticed that attempting to move the resources directory to the
ports repository creates ugly artifacts because that would be the only
content of the base release branches in the ports repo.
Ignore the rename operation from subversion-subport to
larryv-subversion-subports, since that would generate a backup copy of
the old branch.
Since we know that the branches are the same, we can just ignore the
copy.
release_1_4_0-rc1 and release_1_4_0-rc2 did not contain a base folder
because the release_1_4 branch was a copy of trunk/base, not a copy of
trunk with only the base folder.
Fix this by hiding the difference.
Additionally, drop the gimp_1_3_15 tag, which is not needed.
Branches that did no longer exist would previously cause warnings during
the export. This adds explicit rules to ignore those to silence the
warnings.
While reviewing the warnings, I found a number of other branches that
required special handling:
- gsoc14-pip2port was moved to contrib later, let's move its history
there as well.
- subversion-subports was later renamed to larryv-subversion-subports.
Let's hide this rename and treat the branch as if its name had always
been the latter.
- release_1_4 did not contain a single base subfolder like all the other
release branches for a while, but was a complete copy of base. Let's
hide this by converting it back into a copy of base.
We only had a rule for /branches/release_[^/]+, but not for the first
release, which used a different naming scheme.
While at it, fix the naming scheme and rename the branch to release_1_0
to match the other release branches.
Rainer MüllerandRainer Müller
Clemens Lang
Ryan SchmidtandClemens Lang
Rainer MüllerandClemens Lang