Hi. I know that fossil (and most other version control systems) can handle properly only text source files.
I am designing a format for my application and have some questions about the files handling. They are very related, but in different form: What makes the binary files different from the text files? The presence or absence of 0 bytes does not seems to make serious difference for processing by the same algorithms. Or it makes? What properties a file format needs in order to be processed properly by fossil? Is it enough for a file to contains only utf-8 characters or some other properties are mandatory as well? Is it possible to define such binary file format that to be properly processed by fossil (of course, after removing the explicit binary file checks)? Or the opposite question: Is it possible to compose such text file that to not be processed properly by fossil algorithms? -- http://fresh.flatassembler.net http://asm32.info John Found <johnfo...@asm32.info> _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
