https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #28 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Austin English from comment #27) > (In reply to Austin English from comment #26) > > Created attachment 102512 [details] > > try 10, extra sanity checks > > > > try 9 works for me, but I put some extra sanity checks in. In theory, > > someone could have valgrind from svn, and VEX in git svn, or vice versa, and > > try 9 would break with that. > > > > I also added '|| exit 1' to the cd command, as a sanity check / to satisfy > > shellcheck. > > Note: version differences aren't a bug, just checked out at different times > and I was too lazy to sync them :) > > Gentoo/AMD64: > linux-svn: valgrind-3.13.0.SVN-16159M-vex-3285 > linux-git-svn: valgrind-3.12.0.SVN-16107-vex-3276 > > OS X Sierra: > mac-svn: valgrind-3.13.0.SVN-16159M-vex-3285 > mac-git-svn: valgrind-3.12.0.SVN-16107-vex-3276 Thanks for the test. Strange that the git-svn version does not show a M(odified) marker. -- You are receiving this mail because: You are watching all bug changes.
