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

Re: Subversion 1.9: svn cp --pin-externals may produce dummy logentries

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 28 Apr 2015 16:06:17 +0200

On Thu, Apr 23, 2015 at 05:46:29PM +0100, Julian Foad wrote:
> Bert Huijben wrote:
> > I don't think this is really a noop change. Most likely svnadmin dump will
> > show that it recorded a change on the fs layer.
> >
> > The replay API (such as used by svnsync and svnrdump) probably won't show a
> > change.
>
> Erm... but that's basically what 'no-op change' means, to me: when a
> 'change' is noted at the FS layer (and seen in a dump) but the 'after'
> content is the same as the 'before' content, and no change is reported
> by 'replay' and similar higher level APIs.
>
> The 'content' concerned could in principle be file text, properties,
> directory entries, or any combination. In practice usually we see an
> issue either with file text or with properties.
>
> - Julian

Should be fixed as of http://svn.apache.org/r1676538
Received on 2015-04-28 16:07:40 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.