I guess we should question the assumption that both revision and the
svn:date property associated with the revision should be monotonically
increasing. To me, they are separate concepts, can use separate persistent
storage, and can use separate indices for sort/search and retrieval.

Greg Hudson wrote:
> There are sane people who think you shouldn't be importing version
> control history into an existing non-empty repository.

Unfortunately, there are many cases where that is impossible to avoid
(we will have that situation at $WORK sometime soon). In theory, it
should be possible to merge two repositories such that both revision and
svn:date are both monotonically increasing. In practice, however, doing
if via dumpfile manipulation is an exercise in extreme frustration (as
is the closely related task of reorganizing a repository layout via
rewriting the dumpfile).

I have some thoughts about how to accomplish such magic (using the ra
replay functionality to talk to the repo's directly probably), but there
are not enough hours in the day to accomplish what I want to do now, let
alone take on a task of such magnitude. I might be able to (at some
indefinite point in the future) sit down and sketch out a design
document for a transformation tool that would do all this and more. No
promises, though; I still have uncommitted merge changes from OSCON2008
to the perl-bindings-improvement branch that I need to finish... :(