On Sat, Aug 5, 2017 at 6:40 AM, Warren Young wrote:
> I’ve seen such errors when both “fossil server” and “fossil sync” are
> trying to use the same file.
>
Note that the file being locked is the global config file, so it might(?)
be a fossil process unrelated to this repo which is the problem.
Hi,
I'm new to fossil and I find that the component mkversion would crash if input
wrong files, e.g., "$./mkversion wrong_file_1 wrong_file_2 wrong_file_3” will
trigger a segfault.
I think it would be better if mkversion could exit gracefully with proper log
messages. Attached please find the pa
On 8/5/17, jiazhouyan...@sina.com wrote:
> Hi,
> I'm new to fossil and I find that the component mkversion would crash if
> input wrong files, e.g., "$./mkversion wrong_file_1 wrong_file_2
> wrong_file_3” will trigger a segfault.
> I think it would be better if mkversion could exit gracefully with
3 matches
Mail list logo