Issue triage: issues 3429 and 3474

Hi,

I recently verified that the following two issues are fixed on trunk:

- #3429: "svn mv A B; svn mv B A" generates replace without history

- #3474: making a new subdir, moving files into it and then renaming
the subdir, breaks history of the moved files

Should I mark these as fixed in the issue tracker, or will someone
else do that, after double-checking my findings?

Or, maybe the best approach: I could add a regression test for these
issues, so we can all be sure that they are fixed (and remain fixed),
after which they can be marked as fixed.

I have not written a test for Subversion before, but I guess I should
be able to manage after reading the relevant section from the
community guide, and the subversion/tests/README and
subversion/tests/cmdline/README it references. Any other pointers or
tips are welcome of course :-).

Cheers,

-- 
Johan