On Tue, Oct 15, 2019 at 2:40 AM Julian Foad wrote:
> Your analysis is good enough for me. I don't need to double check the details.
>
> I'd say, add a short summary and a link to that email, and close it.
Will do...
FWIW I tested the SVN-1722 reproduction script on 1.13.0-rc1 earlier
today and a
On 2019/10/16 10:36, Daniel Shahaf wrote:
Yasuhito FUTATSUKI wrote on Tue, Oct 15, 2019 at 16:19:46 +0900:
On 2019-10-15 07:04, Daniel Shahaf wrote:
Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
On 2019/10/13 7:24, Daniel Shahaf wrote:
Also, what about the svnadmin_tests.py pat
Johan Corveleyn wrote on Wed, Oct 16, 2019 at 01:07:32 +0200:
> I did have some trouble testing it with Python 3.7 though:
>
> - First, I had to try it on the swig-py3 branch, because on trunk I
> get this when trying to run any test with py 3.7:
⋮
> I guess that's one of the issues fixed by the s
Yasuhito FUTATSUKI wrote on Tue, Oct 15, 2019 at 16:19:46 +0900:
> On 2019-10-15 07:04, Daniel Shahaf wrote:
> > Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
> > > On 2019/10/13 7:24, Daniel Shahaf wrote:
>
> > > I see. Now I agree it would suffice here.
> > > > So, how about:
> > >
On Tue, Oct 15, 2019 at 6:20 PM Yasuhito FUTATSUKI wrote:
>
> On 2019-10-15 17:17, Johan Corveleyn wrote:
> > On Tue, Oct 15, 2019 at 9:26 AM Yasuhito FUTATSUKI
> > wrote:
> >>
> >> On 2019-10-15 07:04, Daniel Shahaf wrote:
> >>> Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
>
Robert Dailey wrote:
I am trying to cross-compile the subversion library for Android using
the Android NDK.
I would love to see a successful Android build of svn client (and/or of
a svn server).
Just to set your expectations: as far as I am aware, nobody has
previously been talking about it
Hello,
I am trying to cross-compile the subversion library for Android using
the Android NDK. I have the toolchain properly set up, I think, but
I'm getting a strange error during `./configure`:
```
checking build system type... x86_64-unknown-linux-gnu
checking host system type... configure: err
On 2019-10-15 17:17, Johan Corveleyn wrote:
On Tue, Oct 15, 2019 at 9:26 AM Yasuhito FUTATSUKI wrote:
On 2019-10-15 07:04, Daniel Shahaf wrote:
Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
On 2019/10/13 7:24, Daniel Shahaf wrote:
I see. Now I agree it would suffice here.
S
On Tue, Oct 15, 2019 at 9:26 AM Yasuhito FUTATSUKI wrote:
>
> On 2019-10-15 07:04, Daniel Shahaf wrote:
> > Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
> >> On 2019/10/13 7:24, Daniel Shahaf wrote:
>
> >> I see. Now I agree it would suffice here.
> >>
> >>> So, how about:
> >>>
> >>
On 15.10.2019 09:10, Julian Foad wrote:
> Branko Čibej wrote:
>> [...] if the dump or the load step drops no-op
>> changes, all existing working copies suddenly are no longer compatible
>
> No. They remain compatible.
>
> (Perhaps you are thinking of eliminating no-op commits and renumbering re
On 2019-10-15 07:04, Daniel Shahaf wrote:
Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
On 2019/10/13 7:24, Daniel Shahaf wrote:
I see. Now I agree it would suffice here.
So, how about:
1. Make the test use non-binary mode for changing and reading the
file 'lambda'.
2
Branko Čibej wrote:
> [...] if the dump or the load step drops no-op
> changes, all existing working copies suddenly are no longer compatible
No. They remain compatible.
(Perhaps you are thinking of eliminating no-op commits and renumbering revs.
That's not what we're talking about.)
- Jul
12 matches
Mail list logo
