stant(d, "SVN_VERSION",SWIG_FromCharPtr("1.8.0
(r1212357)"));
subversion-nightly/subversion/include/svn_version.h:#define SVN_VER_TAG
" (r1212357)"
subversion-nightly/subversion/include/svn_version.h:#define
SVN_VER_REVISION 1212357
Shane
On December-08-11 2:
11:43, Hyrum K Wright wrote:
On Wed, Dec 7, 2011 at 11:29 AM, Stefan Sperling wrote:
On Wed, Dec 07, 2011 at 11:23:30AM -0400, Shane Turner wrote:
Should I open a bug report to have the packages regenerated,
No. Releases are never regenerated. That would invalidate signatures
developers sent fo
Should I open a bug report to have the packages regenerated, assuming
that will fix the problem? I would take a look at the scripts to build
the source archives if I knew where they were.
Shane
On 06/12/2011 12:28 PM, Shane Turner wrote:
subversion/include/svn_version.h is incorrect as well
11 at 7:47 AM, Shane Turner <mailto:shane.tur...@newpace.ca>> wrote:
I was just taking a look at the differences between Subversion
1.7.1 and 1.7.2 and noticed a couple of diffs that look odd.
In subversion/bindings/swig/python/core.c and
subversion/bindings/swig/ruby/cor
cluded the diff below. I've filtered out all of the path
differences in the comments ("/*@SWIG:...").
Shane Turner
diff -rwB -I '.*@SWIG:.*'
subversion-1.7.4bed3649c532/subversion/bindings/swig/python/core.c
subversion-1.7/subversion/bindings/swi
5 matches
Mail list logo