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

Re: Subversion semantics: no no-op changes

From: Julian Foad <julianfoad_at_apache.org>
Date: Mon, 14 Oct 2019 10:22:46 +0100

Eric S. Raymond wrote:
> Julian Foad <julianfoad_at_apache.org>:
>> [...] I have come across a number of kinds of what could
>> be called a "no-op change" or perhaps better described as "I touched this
>> but did not change its value".
> No-op commits are specifically awkward for

Eric, thank you for your thoughts on no-op commits.

Unfortunately I failed to make clear that I didn't mean to talk about an
entire commit that is in total a no-op. That is of course one
manifestation of a no-op change, and I would certainly be interested in
discussing it.

However, in this thread I specifically meant to talk about all the
possible variants of micro-change within a commit (or within a diff or
update or merge or ...). For the sake of simplicity, let's say we're
talking about a commit that also contains at least one "operative" change.

- Julian
Received on 2019-10-14 11:22:48 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.