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

"svnlook diff": the node separator is moved to the bottom of the diff when output is redirected to a file

From: Dang Nguyen <haidangwa_at_comcast.net>
Date: Sun, 29 Jun 2008 08:32:31 -0700

I just installed Subversion 1.5 on Windows Server 2003. We just moved
from Subversion 1.3.2 on Debian. I'm seeing odd behavior with the
"svnlook diff" command on the Windows platform that I didn't see in the
Debian platform -- not sure if it's the OS or if the new version of
Subversion is at fault here.

Basically, when I run "svnlook diff" and let the output go to stdout,
the output is fine. I see the usual node separator followed by the
diffs. When the same command is redirected into a file, then each
node's separator is moved to the bottom of the node's diffs.

My command line:
    svnlook.exe diff <repospath> -r 308 > out.txt

Below are the contents of the output file.

--- trunk/scripts/commit-hooks.build 2008-06-29 07:06:50 UTC (rev 307)
+++ trunk/scripts/commit-hooks.build 2008-06-29 07:38:55 UTC (rev 308)
@@ -47,10 +47,10 @@
                 <include name="${revlogfile}"/>
- <echo message="&#013;&#013;" file="${diff_file}" />
+ <echo message="&#013;&#013;" file="${msgbody}" append="true"/>
         <!-- diff and get the changes in this commit -->
- <exec program="svnlook.exe" output="${diff_file}" append="true"
commandline="diff ${path.repository} -r ${revision} -x -b
--no-diff-deleted --no-diff-added"/>
+ <exec program="svnlook.exe" output="${diff_file}"
commandline="diff ${path.repository} -r ${revision} -x -b
--no-diff-deleted --no-diff-added"/>
         <concat destfile="${msgbody}" append="true">
Modified: trunk/scripts/commit-hooks.build

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-29 23:47:21 CEST

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.