On Sun, Jun 24, 2012 at 11:26 AM, James Bremner <[email protected]>wrote:
> One of my source code files is considered by fossil to be binary. > > Artifact 9c62b051e82f735a46a249047a2b02374247e991 > > File unit_test/unit_test.cpp > 2012-06-22 20:53:14 - part of checkin [a68d8947a6] on branch trunk - cVMG > class > gracefully handles no GPS data; cVMG unit test (user: James ) [annotate] > (file is 9581 bytes of binary data) > > This isn't a huge problem, but I would like to know: > > 1. Why did this happen? > Your file either contains a \000 character, or else it has a single line of text that is longer than 8191 characters. > > 2. Can I persuade fossil that this file is really text? > The only part of Fossil that cares is the "diff" logic. And, no, if your file contains a \000 character or a line longer than 8191 charaters, then there is no way to convince "diff" to ignore that fact. The "diff" logic is used for the "diff" command (obviously) but also for "annotate" and "merge". > > James > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
