[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: No no-op changes

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 19 Sep 2014 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:
> * 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?


- Julian
Received on 2014-09-19 17:34:40 CEST

This is an archived mail posted to the Subversion Dev mailing list.