Re: [fossil-users] Veracity (was: Fwd: suggestion on fossil)
Date: Thu, 20 Oct 2011 01:45:30 +0200 From: Joerg Sonnenberger jo...@britannica.bec.de To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Veracity (was: Fwd: suggestion on fossil) Message-ID: 20111019234530.gb10...@britannica.bec.de Content-Type: text/plain; charset=us-ascii On Wed, Oct 19, 2011 at 06:42:21PM -0400, Richard Hipp wrote: The only problem with binary files is that you cannot merge them. Even that is not necessarily true. You can't merge binary files like text files -- sure. But it doesn't mean that for a specific binary format, a merge algorithm isn't possible. Consider ODF documents for a moment. A merge program could extract the zip archive, do a *textual* merge on the XML files and zip the result up again. It works well for many use cases. Joerg Since ODF documents can be unzipped, and their XML contents are text anyway, why not make a commit program (instead of a merge program) that unzips the ODF and stores the XML in the repo ? Jos van Kesteren. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Has any fossil user ever experienced a SHA1 collision?
Dear fellow fossil-users ? As we all know, SHA1 and its successor algorithms are specifically designed to make collisions not just improbable, but very very very improbable. However, there are a lot of fossil users doing lots and lots of commits and other stuff that involves lots and lots of SHA1 calculations, so we could look at fossil not just as being a DVCS, but also as a kind of SHA1 collision search engine :-) Just for the sake of my curiosity; is there any fossil user out there who has encountered a SHA1 collision ? Does fossil contain code to cope with such a situation ? ( Yes, I know that there are a couple of dedicated machines out there burning lots of CPU-cycles in search of such a collision, but maybe they can't find it just because they look too hard :-) ) Cheers, JvK ___ 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] Help install fossil as window service
Hi Steeve, I recently installed fossil as a Windows service on my own PC. You need a utility like Srvany or (like I did) NSSM to do that. Here are the steps that I took: To arrange this on a Windows box, do the following: Put all repository-files in one single directory (e.g. C:\fossil) , and set the extensions for all repository-files to '.fossil'. (See also: the Fossil server command). You can then start a server manually, e.g. by typing the command fossil server c:\fossil However, you can also install this command as a Windows service, using a utility like Srvany or Nssm. This has the advantage that you don't need to type the command everytime you start up your PC, and that you can not stop the server by accident (by closing all windows in the taskbar) Installing the service using NSSM Enter the command nssm install fossilsrv c:\bin\fossil.exe server c:\fossil ( I also remember having done some manual registry tweaks, but I cannot recall them exactly anymore. Anyhow, the relevant registry settings should look as shown below. ) === Registry settings [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\fossilsrv] ImagePath=C:\bin\nssm.exe run [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\fossilsrv\Parameters] AppDirectory=c:\fossil Application=c:\bin\fossil.exe AppParameters=server c:\fossil [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\fossilsrv\Parameters\AppExit] @=Restart == End of registry settings Kind regards, Jos van Kesteren ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
