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: > * partial repository replication via svnsync due to visibility
You mean resulting in empty revisions? Not a problem. I repeat from my original post: "The ability to commit a new revision with no changes is fine -- a new revision number in Subversion does not imply a change." > * empty revisions via svndumpfilter Empty revisions are not a problem. > * dumps with no-op changes would become invalid? No. - Julian
