On 31.10.2018 21:08, Daniel Shahaf wrote:
> br...@apache.org wrote on Wed, 31 Oct 2018 19:42 +:
>> +++ subversion/trunk/CHANGES Wed Oct 31 19:42:05 2018
>> @@ -26,6 +26,7 @@ https://svn.apache.org/repos/asf/subvers
>> +* Storing passowrds in plain text on disk is disabled by default
>> (r1
br...@apache.org wrote on Wed, 31 Oct 2018 19:42 +:
> +++ subversion/trunk/CHANGES Wed Oct 31 19:42:05 2018
> @@ -26,6 +26,7 @@ https://svn.apache.org/repos/asf/subvers
> +* Storing passowrds in plain text on disk is disabled by default
> (r1845377)
Typo "passwords"
Other issue: In the t
On 2018/10/31 06:54:35, Daniel Shahaf wrote:
> Good morning Ruediger,
>
> rpl...@apache.org wrote on Wed, 31 Oct 2018 06:45 +:
> > Adjust grep syntax to be able to run it with Perl 5.16.3.
> >
> > * tools/dist/backport.pl
> > (vote) Adjust grep syntax to be able to run it with Perl 5.1
On Wed, Oct 31, 2018 at 6:14 AM Thomas Singer
wrote:
> Hi all,
>
> OK, we are now at SVN 1.11 because you have agreed to release often with
> only a few changes. What does the prefix "1." mean - will there be some
> "2." or "3." in the future? If not, then it is redundant. For time-based
> releas
On Wed, Oct 31, 2018 at 09:46:23AM +, Jonathan Guy wrote:
> Hi Stephan
> Thanks for the reply.
> I did see code section you refer to however the svn_client__resolve_conflicts
> will only be called if you have ctx->conflict_func2.
> That function (AFAIK) is only installed if an “accept” option
On 31.10.2018 13:01, Julian Foad wrote:
> Stefan Sperling wrote:
>> On Wed, Oct 31, 2018 at 02:49:57AM +0100, Branko Čibej wrote:
>>> Given that we support a number of secure credentials stores, I
>> propose
>>> that, starting with 1.14.0 LTS, we disable the on-disk plain-text
>>> password store by
Stefan Sperling wrote:
>On Wed, Oct 31, 2018 at 02:49:57AM +0100, Branko Čibej wrote:
>> Given that we support a number of secure credentials stores, I
>propose
>> that, starting with 1.14.0 LTS, we disable the on-disk plain-text
>> password store by default.
>
>Why not start with 1.12.0?
+1 to do
On 31.10.2018 11:13, Thomas Singer wrote:
> Hi all,
>
> OK, we are now at SVN 1.11 because you have agreed to release often
> with only a few changes. What does the prefix "1." mean - will there
> be some "2." or "3." in the future? If not, then it is redundant. For
> time-based releases, wouldn't
What does the prefix "1." mean
Major versions are usually used to denote API versions. It is expected that on
at least some level, all minor revisions of version 1 are somewhat compatible
to each other, bar new features introduced in later minor revisions.
Conversely, there is no expectation th
Hi all,
OK, we are now at SVN 1.11 because you have agreed to release often with
only a few changes. What does the prefix "1." mean - will there be some
"2." or "3." in the future? If not, then it is redundant. For time-based
releases, wouldn't it be more useful to use the year, e.g. the next
Hi Stephan
Thanks for the reply.
I did see code section you refer to however the svn_client__resolve_conflicts
will only be called if you have ctx->conflict_func2.
That function (AFAIK) is only installed if an “accept” option is supplied as
the code below
/* Install a legacy conflict handler
On Tue, Oct 30, 2018 at 06:39:49PM +, Jonathan Guy wrote:
> [[[
> *subversion/svn/merge-cmd.c
> (svn_cl__merge): Suppress the interactive conflict resolver
> if a merge has been performed with the dry-run option.
> ]]]
Hi Jonathan,
Thank your for the patch. I am afraid I misled you earlier b
On Wed, Oct 31, 2018 at 02:49:57AM +0100, Branko Čibej wrote:
> Given that we support a number of secure credentials stores, I propose
> that, starting with 1.14.0 LTS, we disable the on-disk plain-text
> password store by default.
Why not start with 1.12.0?
13 matches
Mail list logo
