subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <>
Subject Re: Efficient and effective fsync during commit
Date Tue, 16 Jun 2015 22:03:03 GMT
On 15.06.2015 18:24, Mark Phippard wrote:
> On Mon, Jun 15, 2015 at 12:15 PM, Branko ─îibej <
> <>> wrote:
>     On 15.06.2015 17:36, Ivan Zhakov wrote:
>     > On 12 June 2015 at 15:11, Stefan Fuhrmann
>     <
>     <>> wrote:
>     >> To be clear: You are proposing that the code on Windows
>     >> is fundamentally broken (revision contents not being
>     >> committed) while I think we "only" have a persistence
>     >> issue with renames. Since your business depends on
>     >> you being wrong, it would be in your best self-interest
>     >> to go and find out ...
>     >>
>     >> Of course, I could apply for an MSDN subscription, wait
>     >> for it be approved etc. but I think it would be fairer if you
>     >> could check the Windows side of things while I try to get
>     >> some answers for POSIX.
>     >>
>     > Am I understand you properly, that *your business* does not
>     depend on
>     > Windows and you just do not care about this
>     Ahem. So ... this has gone somewhat off the straight and narrow. Let's
>     leave business and self-interest out of this (all parties) and look at
>     the actual problem instead.
>     We've always sort of assumed around here that whoever had the working
>     configuration/platform on hand would be more likely to be able to
>     verify
>     some platform-dependent edge case or other. Windows is decidedly a bit
>     of a special case because, traditionally, setting up a build and test
>     environment for Subversion has been horribly complicated (as I handily
>     reminded myself just the other day as I was setting up a VM to get a
>     Windows vote in for 1.9.0-rc2 ... and I'll happily admit part of
>     the blame).
>     Stefan, for the future, I do think it wouldn't hurt you to get
>     your MSDN
>     subscription and set up a build environment if you intend to make
>     platform-dependent changes that can't be verified otherwise.
>     That's just
>     common sense. As it's also common sense for Ivan to verify such
>     changes
>     instead of placing all the burden on you.
> Not to go too far off-topic, but is it even true that you still need
> MSDN?  I thought the compilers and build tools were available for free
> now?  There is even a free version of Visual Studio that is fully
> functional.
> Before this was available, I recall the SDK now includes the compilers
> and that is also freely available.

Versions of compilers and Visual Studio are available for free, yes. You
still have to build a Windows machine or VM; the MSDN subscription that
is available to all ASF committers gives you the ability to do that
legally and for free.

-- Brane

View raw message