> W dniu 2013-10-04 15:04, Ivan Zhakov pisze: > > On 4 October 2013 17:00, Karol Szkudlarek <ka...@mikronika.com.pl> > wrote: > >> W dniu 2013-10-04 14:50, Ivan Zhakov pisze: > >> > >>> On 4 October 2013 16:44, Ivan Zhakov <i...@visualsvn.com> wrote: > >>>>> I'm trying to use the latest 1.8.3 64-bit version of svn client: > >>>>> > >>>>> CollabNetSubversion-client-1.8.3-1-x64.exe > >>>>> > >>>>> but several times crashes. In attachement are log and dmp. > >>>> Hi, > >>>> > >>>> The attached dumps and logs doesn't have debug symbols included, > >>>> this we're unable to investigate the issue. I recommend you contact > >>>> company produced this binaries (CollabNet) or try to reproduce > >>>> problem with other Subversion binaries distribution and contact them. > >>>> > >>> Well, I checked logs more carefully and it seems like issue #4425 > >>> [1] which is fixed in r1522892 and proposed for backport to > >>> Subversion 1.8.4. > >>> > >>> [1] http://subversion.tigris.org/issues/show_bug.cgi?id=4425 > >>> > >> Well, yes it looks like exactly my problem. Thanks for info about. > >> When the > >> 1.8.4 will be released? > >> Now its very annoying crash. I do 'svn log' very often. :-) > > There is no specific schedule for patch releases. Usually they come > > not less often than every month and if important fixes are waiting for > > release. Subversion 1.8.3 was released 29 August 2013. > > > Hello again Ivan, > > Now we have 14 of October (so we have roughly more then 1 month from > 1.8.3 release) and I'm still stuck with crashes of subversion 1.8.3. > Please tell me ss it possible to back to 1.7.x series or not?!
Of course it is. Of course, there is no way to downgrade a working copy that I am aware of, so you would have to do a clean checkout. BOb > Or somebody from subversion release managers could answer me my > question about when will be 1.8.4 released with fix for #4425?! > > Regards, Karol Szkudlarek > > > -- > Karol Szkudlarek > Head Of Software Development > DCIO > > Mikronika, HQ Poznan > > Please consider your environmental responsibility. > Before printing this e-mail message, ask yourself whether you really need a > hard copy.