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

Re: svn log says text-mods="true" but there are no diffs

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 04 Dec 2020 20:41:27 +0000

Vincent Lefevre wrote on Fri, 04 Dec 2020 01:08 +00:00:
> I get the following:
>
> $ svn log --xml -v -r 1984 https://scm.gforge.inria.fr/anonscm/svn/mpfr
> <logentry
> revision="1984">
> <author>vlefevre</author>
> <date>2002-07-23T16:22:08.000000Z</date>
> <paths>
> <path
> prop-mods="false"
> text-mods="true"
> kind="file"
> action="M">/trunk/mul.c</path>
> </paths>
> <msg>Fixed permissions.
> </msg>
> </logentry>
> </log>
>
> I'm wondering why text-mods="true" while
>
> svn diff -c 1984 https://scm.gforge.inria.fr/anonscm/svn/mpfr
>
> shows no diffs.

You may be running into this (quoting from svn_fs_contents_changed()'s docstring):

 * @note svn_fs_contents_changed() was not designed to be used to detect
 * when two files have different content, but really to detect when the
 * contents of a given file have changed across two points in its history.
 * For the purposes of preserving accurate history, certain bits of code
 * (such as the repository dump code) need to care about this distinction.
 * For example, it's not an error from the FS API point of view to call
 * svn_fs_apply_textdelta() and explicitly set a file's contents to exactly
 * what they were before the edit was made. We have a pair of functions
 * that can answer both of these questions, svn_fs_contents_changed() and
 * svn_fs_contents_different(). See issue 4598 for more details.

Or maybe that revision was created by a pre-1.0 version of Subversion
that had some bug or another.
Received on 2020-12-04 21:41:55 CET

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

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