(2) is the best path for USERS of subversion. More toggles is mired in risk
and adding complexity. Improvements should "just work" out the box - unless
there is some technical hurdle. A 25% increase in disk usage is nothing
today for even a fraction more speed on operations happening thousands of
On Fri, Aug 18, 2017 at 05:33:14PM +, Daniel Shahaf wrote:
> s...@apache.org wrote on Fri, 18 Aug 2017 10:33 +:
> > +++ subversion/site/publish/security/CVE-2017-9800-advisory.txt Fri Aug 18
> > 10:33:10 2017
> > @@ -80,24 +96,36 @@ Recommendations:
> >the included patch.
> >
> >
Would it be useful to have a mailing list dedicated for communications
between us (upstream developers) and various downstream packagers and
distributors?
I suppose this basically boils down to whether downstream
packagers/distributors are happy to follow this list (or users@, which
we
s...@apache.org wrote on Fri, 18 Aug 2017 10:33 +:
> +++ subversion/site/publish/security/CVE-2017-9800-advisory.txt Fri Aug 18
> 10:33:10 2017
> @@ -80,24 +96,36 @@ Recommendations:
>the included patch.
>
>3. Clients that are not able to execute the 'ssh' command are not
>
On Aug 18, 2017, at 11:47 AM, Johan Corveleyn wrote:
>
> I agree a more integrated collaboration environment would a big plus.
> But ... how do we get there? Without losing our independence as an ASF
> project ...
>
> Can we get there with ASF infrastructure? I doubt it. I've
On Thu, Aug 17, 2017 at 5:21 PM, Jacek Materna wrote:
> I mentioned earlier on past thread, and still stand by the statement
> that setting up a collaborative space beyond email is key to
> attracting, enabling and growing an active beta testing user base who
> is committed to
On Sun, Jan 29, 2017 at 10:35 AM, Stefan Fuhrmann wrote:
> On 24.01.2017 12:20, Stefan Sperling wrote:
...
>> I would like to get an 1.10.0 alpha1 released in February. Unless I hear
>> objections I will start rolling this alpha release from trunk and call a
>> vote on it
7 matches
Mail list logo