RE: svnversion output changed when redirecting the output. Why?
From: Bert Huijben <bert_at_qqmail.nl>
Date: Thu, 11 Feb 2016 13:29:53 +0100
This is a known issue with some slightly older builds of TortoiseSVN.
Please upgrade and otherwise (re-)report the issue at the TortoiseSVN project as this is (was) caused by their specific build scripts.
This issue is (was) caused by linking and using multiple CRT instances inside the same program, causing undefined behavior inside Visual C++ code.
Bert
From: Steenveld, Andre [mailto:A.H.M.Steenveld_at_marin.nl]
Hi,
I’m working with svn (via TortoiseSVN) versions 1.7, 1.8 and 1.9 and due to external factors I cannot bring it up to the same version.
Also, I’m using svn via the TortoiseSVN package but I believe that my question is related to svn and not to TortoseSVN, please correct me it this is not the case.
I use the svnversion command to keep track of versions in my sandboxes. For this I redirect the output from svnversion to a file and use that file in other parts.
For versions 1.7 and 1.8 the command line output from svnversion is identical to the redirected output. But for version 1.9 it is not and there is no command line option to get it to the `old style’ output.
Here is an example for 1.8
C:\…> svnversion .
22923:22924M
C:\...>svnversion . > output.txt
C:\...>type output.txt
22923:22924M
And here is the same example but now for 1.9
C:\…> svnversion .
22923:22924M
C:\...>svnversion . > output.txt
C:\...>type output.txt
M
22923:22924
Note that if the sandbox is not modified the first line is an empty one.
Question:
Why is the M (sandbox modified) on a separate line?
How do I get ‘1.8’ behavior back for this 1.9 version of svnversion?
Kind regards.
André Steenveld | Software Engineer | Production Onderhoud, Ontwikkeling & Support
<https://www.linkedin.com/company/marin> <http://www.youtube.com/marinmultimedia> <https://twitter.com/MARIN_nieuws> <https://www.facebook.com/marin.wageningen>
|
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.