On Fri, Jul 13, 2018 at 05:12:04PM +0100, Julian Foad wrote:
> I guess previous release managers merged the relevant changes manually to
> achieve this.
I ran a sync merge from trunk/CHANGES to branch/CHANGES, and manually
deleted any entries above the one for the release being prepared.
This wo
Hello. This patch fixes svn copy behaviour. Let's discuss.
What are my next steps here? Can I help somehow with patch acceptance?
12.07.2018, 01:19, "Nikita Slyusarev" :
> [[[
> Correctly handle existing parent directories when performing repos-to-wc copy.
>
> * subversion/libsvn_client/copy.c
>
On 14 July 2018 09:08:12 BST, Stefan Sperling wrote:
>On Fri, Jul 13, 2018 at 05:12:04PM +0100, Julian Foad wrote:
>> I guess previous release managers merged the relevant changes
>manually to achieve this.
>
>I ran a sync merge from trunk/CHANGES to branch/CHANGES, and manually
>deleted any entri
On 13.07.2018 19:43, Daniel Shahaf wrote:
> Julian Foad wrote on Fri, 13 Jul 2018 17:12 +0100:
>> $ svn ls ^/subversion
>> README
>> branches/
>> developer-resources/
>> site/
>> site-ng/
>> svn-logos/
>> tags/
>> trunk/
>> upstream/
>>
>> Brane's suggestion of locating CHANGES in the web site tree
Nikita Slyusarev wrote on Sat, Jul 14, 2018 at 13:19:54 +0300:
> Hello. This patch fixes svn copy behaviour. Let's discuss.
> What are my next steps here? Can I help somehow with patch acceptance?
The submission includes a log message and an explanation of the problem. In
that regard it is comple
14.07.2018, 17:18, "Daniel Shahaf" :
> It would help to add a regression test to subversion/tests/cmdline/ or
> subversion/tests/libsvn_client/.
Thanks for your advice. I've added cmdline tests to the patch and fixed the log
message accordingly.
[[[
Correctly handle existing parent directories wh
On 13.07.2018 17:36, Philip Martin wrote:
> Julian Foad writes:
>
>> Philip, can you help clarify this?
>>> It's not clear to me from the added paragraph whether the restriction
>>> "only access the context from a thread at a time" is imposed by the
>>> library implementation or by the way API con
Julian Foad wrote:
> I have decided I will re-roll these releases. Just the CHANGES file will
> be up-to-date, and without changes relating to later minor release lines
> like it was before. There will be no other changes.
Also COMMITTERS file will be up-to-date.
> I will re-roll ASAP; Monday a
Julian Foad wrote:
> I have decided I will re-roll these releases. Just the CHANGES file will
> be up-to-date, and without changes relating to later minor release lines
> like it was before. There will be no other changes.
Also COMMITTERS file will be up-to-date.
> I will re-roll ASAP; Monday a
The 1.9.9 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Note that this is code-wise identical to 1.9.8; only the CHANGES file and
COMMITTERS file are updated and version num
The 1.10.2 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Note that this is code-wise identical to 1.10.1; only the CHANGES file and
COMMITTERS file are updated and version n
11 matches
Mail list logo
