Re: [fossil-users] some questions about fossil-as-document-repo

problem is a lack of diff & merge tools for the particular document format. Given those, any file format can be used well in a SCM. [The lack of such tools for formats such as MS Word and PDF simply boggles the mind. You would think that such formats were never used for serious documentation.

Re: [fossil-users] Needed: volunteer to autoconf Fossil

Michal Suchanek wrote: > Autotools can be installed and operated on Windows like most other > build configuration systems. I'm not sure that's possible without installing a UNIX like shell and set of tools. This is rather foreign for a native MSWin develop

Re: [fossil-users] Needed: volunteer to autoconf Fossil

Martin Gagnon wrote: > All that thread start when someone post about haiku that need different libs > flags in order to > link properly. If a OS like Haiku don't have this jam, all that is pretty > pointless. Pretty easy to port, especially if the OS is similar to U

Re: [fossil-users] Needed: volunteer to autoconf Fossil

han most systems. I'm sticking with Jam for my code, as it's clean and I can now maintain it easily.] Graeme Gill. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] manifest file (3967) is malformed error

it into two or more. I guess the workaround is to do all renames as a separate commit. I've added a ticket (0ff64b0a5f) to track this, as well as a request that "fossil status" show more information about pending renames (040dcddb1e). cheers, Graeme Gill.

Re: [fossil-users] manifest file (3967) is malformed error

[i-1].zName, zName)>=0". It seemed to be comparing one of the renamed files to another file in the old directory (I think old, but could be new - see above about the info output). Graeme Gill. ___ fossil-users mailing list fossil-users@lists.fo

Re: [fossil-users] manifest file (3967) is malformed error

Graeme Gill wrote: > fossil.exe: manifest file (3967) is malformed Has anyone got any suggestion on where to go with this ? Is there a command to fix a corrupted fossil databases ? Is there a way of diagnosing where/why/what is malformed about the manifest ? Should I just give up and us

[fossil-users] manifest file (3967) is malformed error

ifest file (3967) is malformed and fossil diff shows that the file wasn't committed. Questions: 1) What caused this ? 2) How do I fix it ? thanks, Graeme Gill. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://list