[fossil-users] Fuse SIGSEGV

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Was trying to run find, eventually got this: Program received signal SIGSEGV, Segmentation fault. 0x76574230 in __strncmp_ssse3 () from /lib64/libc.so.6 (gdb) ba #0 0x76574230 in __strncmp_ssse3 () from /lib64/libc.so.6 #1

Re: [fossil-users] 2 repos being each others remote-url

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/21/2014 11:48 AM, Michai Ramakers wrote: does it make sense to have 2 repos on different machines having each others remote-url? I can imagine things get a bit weird, sync-tree wise, when more machines are involved, but I couldn't think of a

Re: [fossil-users] 2 repos being each others remote-url

On Thu, Jun 26, 2014 at 1:18 PM, Andy Goth andrew.m.g...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/21/2014 11:48 AM, Michai Ramakers wrote: does it make sense to have 2 repos on different machines having each others remote-url? I can imagine things get a bit weird,

Re: [fossil-users] Fuse SIGSEGV

On Thu, Jun 26, 2014 at 4:01 PM, Andy Goth andrew.m.g...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Was trying to run find, eventually got this: Program received signal SIGSEGV, Segmentation fault. 0x76574230 in __strncmp_ssse3 () from /lib64/libc.so.6 (gdb) ba

[fossil-users] Do the default binaries use mingw files? [or what build method was used?]

Just a quick question. :) Regarding the binaries for Windows: http://www.fossil-scm.org/download.html Do these binaries (for Windows) use mingw files? or are they entirely MSVC? (Or, in other words, which of the several build methods were used for the binaries?) Based on the compiling

[fossil-users] Generous time formats

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fossil accepts dates with days beyond the end of the month, so long as the day is not 32 or greater. It also accepts times 24:00:00 through 24:59:59. For example, 2014-02-31T24:59:59 is valid. I imagine it means 31 days after the start of the day

Re: [fossil-users] Fuse SIGSEGV

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/26/2014 3:39 PM, Richard Hipp wrote: Since you are able to repro this, can you rebuild Fossil w/o the -O2 option (so that variables are not optimized out) and rerun in the debugger yet again, then do the same analysis? I have done so, but I

[fossil-users] Incorrect error message for [fossil pull]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [fossil pull -R repos] prints Usage: fossil pull URL when the repository doesn't have a known remote URL. I believe the problem is on line 147 of sync.c in the current Fossil version (cfb8d6604f8a159e8a5c1fa8843be12060f0fff4). - -- Andy Goth |

Re: [fossil-users] Incorrect error message for [fossil pull]

Thus said Andy Goth on Thu, 26 Jun 2014 19:25:05 -0500: [fossil pull -R repos] prints Usage: fossil pull URL when the repository doesn't have a known remote URL. I believe the problem is on line 147 of sync.c in the current Fossil version Do you mean that the Usage statement should