In theory, incremental hotcopy of a Berkeley DB repository can be done by
squirreling away a base hotcopy (datafiles + logfiles), and then incrementally
copying only (but *all* of) the Berkeley DB logfiles thereafter.  The logfiles
are designed to be such that they can be replayed in sequence to enact their
changes to the BDB datafiles.  So incremental hotcopy N+1 might copy the BDB
logfiles which are newer than those captured in hotcopy N, then replay those
logfile actions into the backed-up datafiles.

Unfortunately, the default behavior of 'svnadmin create' is to configure BDB to
automatically remove its unused logfiles (those whose actions have already been
reflected in the datafiles).  One would need to disable that auto-purging
functionality for such an approach to incremental hotcopy to be viable.

See
http://docs.oracle.com/cd/E17276_01/html/programmer_reference/transapp_archival.html
for the official Berkeley DB recommendations.

Forgot the check modified files with native eols (this is on Windows):

Everything works as expected:

>svn blame file-with-NATIVE-eols-WITH-SVN-EOL-STYLE-NATIVE
     9     pburba A
     9     pburba B
     -          - C-MOD
     9     pburba D
     9     pburba E
     9     pburba F

>svn blame file-with-NATIVE-eols
     9     pburba A
     9     pburba B
     -          - C-MOD
     9     pburba D
     9     pburba E
     9     pburba F

Please disregard desc4, it was intended for another issue.

Mass bump of FEATURE issues from 1.8-consider to 1.9-consider (minus a couple
which seem like reasonable options).

Ahem.  Actually change the milestones this time.

Bump all open 1.9-consider issues to 1.10-consider, now that they have missed
the boat for 1.9.