Re: [fossil-users] Whether or not this function examines the entire contents of the blob is officially unspecified.

2013-03-19 Thread Joe Mistachkin
Jan Nijtmans wrote: > > Both NUL-bytes and long lines no longer > abort the function. This has the adverse effect that even > binary files containing NUL bytes are always scanned > completely, even though we know already that the file > is binary. > Actually, given the variety of possible text

[fossil-users] Whether or not this function examines the entire contents of the blob is officially unspecified.

2013-03-19 Thread Jan Nijtmans
This line can be found twice in the fossil source code, and it refers to the functions looks_like_utf8() and looks_like_utf16() (src/diff.c lines 233 and 336). In Fossil 1.25 and earlier, looks_like_utf8/16 bailed out as soon as either a NUL byte or a long line was encountered. Stopping at long l

Re: [fossil-users] Bad link to 'Add attachment' in timeline

2013-03-19 Thread Stephan Beal
On Mon, Mar 18, 2013 at 7:19 PM, Lluís Batlle i Rossell wrote: > Example: > > http://fossil-scm.org/index.html/timeline?u=stephan&c=2013-01-25+17%3A41%3A18&nd&n=2 > (Look for "Add attachment" and click the attachment link). > > I'm not sure how to fix it. Simply remove %R in these two lines? > > h