Re: Official way to create an empty revision

2014-10-01 Thread Konstantin Kolinko
2014-10-02 2:59 GMT+04:00 Daniel Shahaf : > Julian Foad wrote on Wed, Oct 01, 2014 at 10:52:42 +0100: >> Daniel Shahaf wrote in the thread "No no-op changes": >> > Should we provide an "official" way to create an empty revision? That >> > is, a revision whose changed-paths list is empty? >> > >> >

Re: Official way to create an empty revision

2014-10-01 Thread Daniel Shahaf
Daniel Shahaf wrote on Wed, Oct 01, 2014 at 22:59:53 +: > I don't see what API-consumer-level purpose having the same svn:date > would serve; it seems to me it would suffice to guarantee > > r100 < r101 ≤ r102 ≤ r103 ≤ r104 ≤ r105 < r106 > > (where "x < y" ⇔ "svn:date value of y is yo

Re: Official way to create an empty revision

2014-10-01 Thread Daniel Shahaf
Julian Foad wrote on Wed, Oct 01, 2014 at 10:52:42 +0100: > Daniel Shahaf wrote in the thread "No no-op changes": > > Should we provide an "official" way to create an empty revision?  That > > is, a revision whose changed-paths list is empty? > > > > Use-cases: > > > > 1. Suppose last backup is r

Re: svn commit: r1628762 - /subversion/trunk/subversion/libsvn_fs_fs/low_level.c

2014-10-01 Thread Ivan Zhakov
On 1 October 2014 20:41, wrote: > Author: stefan2 > Date: Wed Oct 1 16:41:46 2014 > New Revision: 1628762 > > URL: http://svn.apache.org/r1628762 > Log: > * subversion/libsvn_fs_fs/low_level.c > (read_change): Fix reporting of the "mergeinfo_mod" flag for changed > paths if th

Re: Official way to create an empty revision

2014-10-01 Thread Julian Foad
I should have said, too: I'm not planning on taking this any further, myself. Anybody that wants to... feel free. (Discuss on this list first, as usual, of course.) - Julian Julian Foad wrote: > Daniel Shahaf wrote in the thread "No no-op changes": >>  Should we provide an "official" way to cre

FSFS changed-paths handling - review

2014-10-01 Thread Julian Foad
I took a look through the FSFS code that deals with the changed-path lists, with a special interest in how it reports no-op changes. In the course of this code inspection I found a number of issues that want clarification and a few possible bugs. I have not tried to produce actual buggy behaviou

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread Mark Phippard
On Wed, Oct 1, 2014 at 11:36 AM, Philip Martin wrote: > Mark Phippard writes: > > > On Wed, Oct 1, 2014 at 10:03 AM, Philip Martin < > philip.mar...@wandisco.com> > > wrote: > >> > >> I can trigger the decompression error on a 5GB REPORT by setting > >> http-bulk-updates=yes on the client side.

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread Philip Martin
Mark Phippard writes: > On Wed, Oct 1, 2014 at 10:03 AM, Philip Martin > wrote: >> >> I can trigger the decompression error on a 5GB REPORT by setting >> http-bulk-updates=yes on the client side. >> >> > This does not really answer the question. > > Was your REPORT 5GB because it had a single fi

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread Mark Phippard
On Wed, Oct 1, 2014 at 10:03 AM, Philip Martin wrote: > "C. Michael Pilato" writes: > > > The log message for r2419 mentions "files" larger than 4Gb, and leads me > > to believe that this problem only affects GETs. But here, Philip avoids > > the term "files" and talks about the "compressed siz

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread C. Michael Pilato
On 10/01/2014 10:16 AM, Philip Martin wrote: > Philip Martin writes: > >> "C. Michael Pilato" writes: >> >>> The log message for r2419 mentions "files" larger than 4Gb, and leads me >>> to believe that this problem only affects GETs. But here, Philip avoids >>> the term "files" and talks about t

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread Philip Martin
Philip Martin writes: > "C. Michael Pilato" writes: > >> The log message for r2419 mentions "files" larger than 4Gb, and leads me >> to believe that this problem only affects GETs. But here, Philip avoids >> the term "files" and talks about the "compressed size". Does the bug >> fixed in r2419

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread Philip Martin
"C. Michael Pilato" writes: > The log message for r2419 mentions "files" larger than 4Gb, and leads me > to believe that this problem only affects GETs. But here, Philip avoids > the term "files" and talks about the "compressed size". Does the bug > fixed in r2419 manifest on any response > 4GB

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread C. Michael Pilato
On 10/01/2014 06:48 AM, Philip Martin wrote: > Andreas Stieger writes: > >> I >> will once again point to the serf issues below and httpd/network config. >> https://code.google.com/p/serf/issues/detail?id=152 >> https://code.google.com/p/serf/source/detail?r=2419 > Andreas identified a bug in serf

Re: [serf-dev] serf errors on responses bigger than 4GB

2014-10-01 Thread Lieven Govaerts
Hi, On Wed, Oct 1, 2014 at 12:48 PM, Philip Martin wrote: > Andreas Stieger writes: > >> I >> will once again point to the serf issues below and httpd/network config. >> https://code.google.com/p/serf/issues/detail?id=152 >> https://code.google.com/p/serf/source/detail?r=2419 > > Andreas identif

serf errors on responses bigger than 4GB

2014-10-01 Thread Philip Martin
Andreas Stieger writes: > I > will once again point to the serf issues below and httpd/network config. > https://code.google.com/p/serf/issues/detail?id=152 > https://code.google.com/p/serf/source/detail?r=2419 Andreas identified a bug in serf that causes decompression to fail when the compresse

Re: No no-op changes

2014-10-01 Thread Julian Foad
Daniel Shahaf wrote: > Should we provide an "official" way to create an empty revision?  That > is, a revision whose changed-paths list is empty? [...] I replied to this in a new thread, "Official way to create an empty revision". - Julian

Official way to create an empty revision

2014-10-01 Thread Julian Foad
Daniel Shahaf wrote in the thread "No no-op changes": > Should we provide an "official" way to create an empty revision?  That > is, a revision whose changed-paths list is empty? > > Use-cases: > > 1. Suppose last backup is r100 and revisions r101:r105 were lost; then > after restoring the backup