> On 19 Sep 2014, at 15:49, Julian Foad <julianf...@btopenworld.com> 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: * partial repository replication via svnsync due to visibility * empty revisions via svndumpfilter * dumps with no-op changes would become invalid? Andreas
