[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: Mon, 22 Sep 2014 13:20:37 +0100

Greg Stein wrote:
> Branko ─îibej wrote:
>> We should do exactly the opposite! We should make sure that even no-op changes
>> always get recorded and reported consistently. [...]
> Agreed.

Hi Greg.

> When you start including ACLs, then r1234 might look different to two people.

A revision can already look different to two people, with the existing path-based authorization mechanism.

> And if it gets elided because it "isn't a change", then one person is going to get
> even more confused when the revision doesn't even appear (rather than "no visible
> changes").

A revision will not get elided just because no changes are visible in it. I was talking about per-node changes. To quote again from my original mail,

"The ability to commit a new revision with no changes is fine -- a new revision number in Subversion does not imply a change."

Similarly, the ability to see or extract a revision with no (visible) changes is and will remain perfectly fine.

- Julian
Received on 2014-09-22 14:21:13 CEST

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