Re: [fossil-users] How to fix repo that has checkin with wrong date

+ ) + ); + db_step(u); + db_reset(u); + for(i=0; i30; i++){ db_step(q); db_reset(q); if( sqlite3_changes(g.db)==0 ) break; db_step(u); 2015-05-21 21:19 GMT+05:00 Alexandr Smolnikov bigcrush.k...@gmail.com: Stephan, thanks. I completely forgot about

[fossil-users] How to fix repo that has checkin with wrong date

I have artifact with wrong date looking like C small\schanges\sfor\sphp5 D 5695-09-08T17:37:16 F config.lua 67e347cc7f7c561dd0623e98b28f3ce16d4c447a F create-service.cmd c84a7bb9b20e3ef5a268e20320d9ac8e6ddb125d F docs/JS-md5.html 9e0282d1357595593e61e583620843b63b2b5c2c F docs/authweb.wiki

Re: [fossil-users] How to fix repo that has checkin with wrong date

: On 5/21/15, Alexandr Smolnikov bigcrush.k...@gmail.com wrote: I have artifact with wrong date looking like C small\schanges\sfor\sphp5 D 5695-09-08T17:37:16 F config.lua 67e347cc7f7c561dd0623e98b28f3ce16d4c447a F create-service.cmd c84a7bb9b20e3ef5a268e20320d9ac8e6ddb125d F docs/JS

Re: [fossil-users] How to fix repo that has checkin with wrong date

Stephan, thanks. I completely forgot about gdrive :) Here is the link to the repo: https://drive.google.com/file/d/0B3-QLrjwC79aQ1Etb1ZKZkRBMVU/view?usp=sharing 2015-05-21 20:50 GMT+05:00 Stephan Beal sgb...@googlemail.com: On Thu, May 21, 2015 at 5:47 PM, Alexandr Smolnikov bigcrush.k

Re: [fossil-users] Cannot set 'autosync' and fossil ignores http_proxy

I'm sorry for the noise. Trunk fossil works OK. My old version hanged when server was down or unreachable (I'm behind proxy) f pull http://bigcrush1.mooo.com getaddrinfo() fails: Name or service not known f pull http://bigcrush.mooo.com hangs... [getaddrinfo() OK but connect() fails]

[fossil-users] Cannot set 'autosync' and fossil ignores http_proxy

1) On 'fossil set autosync off' I got ambiguous setting autosync - might be: autosync autosync-tries 2) fossil ignores 'http_proxy' but honors 'proxy' settings if set manually strace shows that fossil hangs on sendto(-1, ...) All that happened after [32f8da0ce7] check-in