Ian Mordey writes:
> Not that I can spot:
> gutils.h
> G_INLINE_FUNC gint g_bit_nth_lsf (gulong mask,
>gintnth_bit);
> G_INLINE_FUNC gint g_bit_nth_msf (gulong mask,
>gintnth_bit);
> G_INLINE_FUNC
>
>
>
> The types gint, guint should be defined in gtypes.h but the cause of the
> error message may not be use of type itself but something earlier. What
> do the lines around 208 in gutils.h look like? And 121 in gstring.h and
> 114 in gmessages.h. Is there something common between those bits o
>
>
> You are not the first to ask for this, but it is significantly more
> complex than just a backend setting. []
>
Yup, I didn't think about the SHA1 being different. I'll implement it
client-side, just ignore this request.
-ph
Paul Hammant writes:
> It would be great if there were a setting somewhere like:
>
> unzip_these_suffiixes_on_serverside_but_reconstitute_zipped_form_for_client_interop:
> docx, xlsx, pptx
>
> (or 'unzip_rezip_suffixes')
>
>
> So Subversion gets to store the text forms (rather than the zip), with
Ian Mordey writes:
> bash-3.2# suncc -std=c90 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS
> -D_REENTRANT -D_LARGEFILE64_SOURCE -Werror=unknown-warning-option
> -I/opt/WANdisco/include -fast -xO5 -xunroll=20 -I./subversion/include
> -I./subversion -I/opt/WANdisco/include/apr-1 -I/opt/WANdisco/include
>
>
>>
> Awesome. It looks like it's compiling now.
>
I spoke too soon.. Got another compiler error on gnome-keyring. Again, this
works fine on 1.9.x:
bash-3.2# suncc -std=c90 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS
-D_REENTRANT -D_LARGEFILE64_SOURCE -Werror=unknown-warning-option
-I/opt/WANdisc
Evgeny Kotkov writes:
> Stefan Sperling writes:
>
>> "local network" is a rather blurry concept.
>> This will often return FALSE for local wireless connections, for
>> example, because of shared medium contention.
>>
>> I agree that 5msec is a well chosen latency threshold.
>> But why not name t
I understand the process to propose feature requests is to first post the
idea on this forum, then if everyone agrees, post an item to Jira.
I previously wrote a blog entry on Git storing MsOffice document unzipped
(.docx and .xlsx are zips XML and a few things) -
https://paulhammant.com/2015/07/3
Stefan Sperling writes:
> "local network" is a rather blurry concept.
> This will often return FALSE for local wireless connections, for
> example, because of shared medium contention.
>
> I agree that 5msec is a well chosen latency threshold.
> But why not name this function after the question i
Daniel Shahaf writes:
> Hmm. My first instinct would be to make the availability of the
> 'compression' knob coupled, not with the format number but with
> SVN_VER_MINOR, so the rule would be "1.10 recognises the 'compression'
> knob if set; 1.9 ignores it".
>
> That _would_ cause the knob to be
Markus,
Yes, leaving rep sharing enabled is better for another reason that a file
sync agent is *likely* to encounter: someone renames a directory. Remember
I'm not using Subversion client tools to effect a commit.
But...
>. Rep sharing brings its real benefits when equal files are stored
> inde
Stefan Sperling wrote:
> On Wed, Aug 02, 2017 at 06:49:55PM -, kot...@apache.org wrote:
>> +svn_boolean_t
>> +svn_ra_serf__is_local_network(svn_ra_serf__session_t *session)
>> +{
>> + return session->conn_latency >= 0 &&
>> + session->conn_latency < apr_time_from_msec(5);
>> +}
>
> "l
Hi, Paul,
> Here it is - http://imgur.com/a/vBeKi - a more interesting graph.
Yes, more interesting. :-)
And it somehow supports my point that, in some use cases, switching of
deltification and rep sharing do no good.
The benefit of disabling compression is understandable, as it just wastes C
13 matches
Mail list logo
