On Wed, Mar 18, 2015 at 08:57:45PM -0700, Ben Reser wrote:
> This is a pre-release for what will eventually become Apache Subversion
> 1.9.0. It may contain known issues, a complete list of
> 1.9.0-blocking issues can be found here:
>
>
> http://subversion.tigris.org/issues/buglist.cgi?component
We leave mine as NULL in svn_wc_entry_t since 1.0 in this case. libsvn_wc, svn,
and all other users should just handle this properly. Where they don’t there is
a bug, that should be fixed here instead of by redesigning the way we store
binary file conflicts. (Note that there were more cases were
I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download/#pre-releases
The SHA1 checksums are:
cbc62b682e69254f57e40da316ebb7fcf998f56e subversion-1.9.0-beta1.tar.bz2
57142f460c51f33
On Thu, Mar 19, 2015 at 1:21 AM, Julian Foad wrote:
> Bert Huijben wrote:
>> Johan Corveleyn wrote:
>>> Thanks. I get a bit further now. But now it fails with some linker problems:
>>>
>>> [[[
>>> svn_repos-1.lib(commit.obj) : error LNK2019: unresolved external
>>> symbol _svn_editor3p__insert_shi
Bert Huijben wrote:
> Johan Corveleyn wrote:
>> Thanks. I get a bit further now. But now it fails with some linker problems:
>>
>> [[[
>> svn_repos-1.lib(commit.obj) : error LNK2019: unresolved external
>> symbol _svn_editor3p__insert_shims referenced in funct[...]
>
> I'm guessing this is caused b
On Wed, Mar 18, 2015 at 10:53:11PM +0100, Bert Huijben wrote:
> (Extending my original answer)
>
> Mine-full should just be implemented as a simple resolve without changing the
> file. The right 'mine' file is already in the right place on a conflict of a
> binary file.
>
> Creating a copy of a
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: donderdag 19 maart 2015 00:32
> To: Julian Foad
> Cc: dev
> Subject: Re: Playing with svnmover
>
> On Wed, Mar 18, 2015 at 10:09 AM, Julian Foad
> wrote:
> > Johan Corveleyn wrote:
> >>> I intend to take a c
On Wed, Mar 18, 2015 at 10:09 AM, Julian Foad wrote:
> Johan Corveleyn wrote:
>>> I intend to take a closer look soon. But as you know, my definition of
>>> "soon" is a bit ... vague ;-).
>>>
>>> I greatly appreciate your efforts to get "move support" ... moving in svn.
>>
>> First hurdle: I have
> -Original Message-
> From: Stefan Sperling [mailto:s...@elego.de]
> Sent: woensdag 18 maart 2015 15:04
> To: dev@subversion.apache.org
> Subject: 1.8.13 release up for testing/signing
>
> The 1.8.13 release is now up for testing/signing at
> https://dist.apache.org/repos/dist/dev/subve
Summary:
+1 to release
Platform
Mac OS X 10.10.2 Yosemite, build 14C109
Standard dependencies:
Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
APR 1.4.8
APR-Util 1.5.2
zlib 1.2.5
httpd 2.4.9
Python 2.7.6
Perl 5.18.2
ruby
> -Original Message-
> From: Branko Čibej [mailto:br...@wandisco.com]
> Sent: woensdag 18 maart 2015 02:00
> To: dev@subversion.apache.org
> Subject: Re: svn commit: r1667280 - in /subversion/trunk/subversion:
> libsvn_wc/merge.c tests/cmdline/merge_tests.py
>
> On 17.03.2015 22:53, Stef
Summary:
+1 to release
Platform
Mac OS X 10.10.2 Yosemite, build 14C109
Standard dependencies:
Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
APR 1.4.8
APR-Util 1.5.2
zlib 1.2.5
httpd 2.4.9
Python 2.7.6
Perl 5.18.2
ruby
Stefan Sperling wrote:
> The 1.7.20 release is now up for testing/signing [...]
SUMMARY:
+1 to release (Unix)
VERIFIED:
-
SHA1 sums:
f600c68010d2fd9a23fc8c6b659099aedac12900 subversion-1.7.20.tar.bz2
e861f85e9df1b5aca903aa6eda15919c454cbda5 subversion-1.7.20.tar.gz
Comparing the
Stefan Sperling wrote:
> The 1.8.13 release is now up for testing/signing [...]
SUMMARY:
+1 to release (Unix)
VERIFIED:
-
SHA1 sums:
aa0bd14ac6a8f0fb178cc9ff325387de01cd7452 subversion-1.8.13.tar.bz2
437cf662b7ed27d2254aa7ca334fdd74b49262ef subversion-1.8.13.tar.gz
Comparing the
James McCoy writes:
> As reported in Debian[0], using git-svn to clone a Subversion repo will
> reliably crash in Subversion's Perl bindings if there are commits
> touching many files.
>
> [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780246
>
> The original report referenced a private r
The 1.7.20 release is now up for testing/signing at
https://dist.apache.org/repos/dist/dev/subversion
Please add your signatures there.
The anticipated release day is March 31.
Note that libsvn_subr/mergeinfo-test 6 and 10 may have occasional failures
(segfaults) due to a one-byte read past a str
The 1.8.13 release is now up for testing/signing at
https://dist.apache.org/repos/dist/dev/subversion
Please add your signatures there.
The anticipated release day is March 31.
Note that the 1.8.12 release was tagged and then skipped because of failures
in diff_tests.py. These are resolved in 1.8.
On Tue, Mar 17, 2015 at 10:44 AM, Julian Foad
wrote:
> Stefan Fuhrmann wrote:
> > Thanks for the review, Julian! Uncovered a bug and
> > fixed all the things you found:
>
> Thanks.
>
> I've proposed r1665894 and r1667101 for backport to 1.9.x.
>
> I'm not quite sure of the severity of the bug, or
On 18.03.2015 10:36, Branko Čibej wrote:
> On 13.03.2015 13:23, Erik Huelsmann wrote:
>>
>>
>> > These days, I suppose we'd be looking at something like Go,
>> which can
>> > be linked with C/C++ and also natively export functions that can be
>> > called from C/C++.
>>
>> As f
On 13.03.2015 13:23, Erik Huelsmann wrote:
>
>
> > These days, I suppose we'd be looking at something like Go,
> which can
> > be linked with C/C++ and also natively export functions that can be
> > called from C/C++.
>
> As far as I can see, Go always comes with Garbage Colle
Johan Corveleyn wrote:
>> I intend to take a closer look soon. But as you know, my definition of
>> "soon" is a bit ... vague ;-).
>>
>> I greatly appreciate your efforts to get "move support" ... moving in svn.
>
> First hurdle: I have trouble compiling it (on Windows 7, VS 2013).
> Both with "rel
21 matches
Mail list logo
