Julian Foad wrote on Fri, Sep 19, 2014 at 16:34:04 +0100:
> Andreas Stieger wrote:
> >> Julian Foad wrote:
> >> Summary:
> >> * A "no-op change" is not a change.
> >> * Subversion should not report a "no-op change" as a "change".
> >> * We should bear this in mind when designing and reviewing.
> >> * Fixes are needed in a few places.
> > These no-op change scenarios come to mind:
> > * empty revisions via svndumpfilter
> Empty revisions are not a problem.
Should we provide an "official" way to create an empty revision? That
is, a revision whose changed-paths list is empty?
1. Suppose last backup is r100 and revisions r101:r105 were lost; then
after restoring the backup, the admin would create 5 empty revisions.
2. Force an empty revision for whatever reason, such as to make the
revnums sync to something:
2.1. See r3 of the regression test merge_tests.py#125 svnmucc_abuse_1().
2.2. W hen loading our repository to the ASF repository, if Joe had
created 26 empty revisions, then The Offset would have been 840100
rather than 840074, which would make our mental math easier.
Received on 2014-10-01 02:47:57 CEST