Comments | fare: Monotone

fare

Monotone

Sep 28, 2005 13:55

You may remember that I am looking for a solution to the SNAIL problem, which will have to be based on epistemic monotonic logic. Well, monotone offers half of the solution, monotonic logic. And that is also the more useful half to me, considering that the instantaneous latency of my SNAIL networks is actually low: when my computers are connected ( Read more... )

smop, monotone, linux, snail, j820, collaboration, code, versioning, en, hacker

Comments 6

wow dlakelan September 29 2005, 02:00:33 UTC

Hi Fare ( ... )

Re: wow fare September 29 2005, 02:20:07 UTC

(1) monotone would probably be not essentially worse for image editing than any other versioning system. Unless your software allows to keep your modifications in a vector (logical) format, you'll have to deal with lots of ugly raster (bitmap) files if you do heavy editing ( ... )

Re: wow fare September 29 2005, 02:25:03 UTC

Oops. Actually, if it's clever, which I suppose it is, considering the speed of commits on my antique PDA, it will only compute checksums for touched files. So the slightly suboptimal space will be the only problem with managing blobs, not the time to compute hashes. Silly me. Long live user-settable filesystem modified time tags!

Re: wow dlakelan September 29 2005, 03:16:00 UTC

Actually, monotone does hash everything be default, because this is safer than doing anything else[0], and as you've discovered, this is actually not a speed issue these days, except in extreme situations.

You can trade off a tiny bit of safety for extra speed by telling it to trust filesystem mod times:
http://www.venge.net/monotone/docs/Inodeprints.html

-- Nathaniel

[0] Assuming you believe in hashes at all, but if you don't, then you have worse problems with monotone.

Thread 5

stty problem fare September 29 2005, 03:28:01 UTC

The display problem I was experiencing was actually the server and the client both writing to the terminal at the same time. In fact, I wrote coproc monotone ... serve ... >&0 thinking that it would redirect both stdin and stderr like >& usually does, whereas it's a different file-descriptor-redirecting syntax that only redirects stdout. I would have had to do a &0 2>&0. But actually, I only need a 2> /dev/null. So monotone is doing the right thing, and the bug was wholly mine. Oops.
If debugging is the process of removing bugs, then programming must be the process of putting them in. -- Dijkstra