[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: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 22 Sep 2014 09:01:32 -0400

On 09/20/2014 03:56 AM, Branko Čibej wrote:
> We should do exactly the opposite! We should make sure that even no-op
> changes always get recorded and reported consistently. You have to
> remember that repository history is not only about tree snapshots,
> it's also about intent and results. In other words, an audit trail is
> just as important as actual repository contents.

FWIW, this line of thought is consistent with the original FS backend
and dump/load design goals. The guiding principle was about preserving
as much information as we could rather than presuming that we knew what
information did and didn't matter to an administrator. This is why
svn_fs_props_changed() and svn_fs_contents_changed() never bothered to
compare the respective prop/text content, but merely noticed that the
DAG had or hadn't been adjusted.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development
Received on 2014-09-22 15:02:05 CEST

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