On Thu, 2005-10-27 at 19:57 +0200, Jon Bright wrote: > Emile Snyder wrote: > > > > No, this is clearly a bug in monotone. You created a legal file on your > > system in the working copy, and monotone choked and died. Thanks for > > digging and figuring it out, > > An interesting question - should monotone allow you to create any old > filename, or should it restrict you to names with half a chance of being > cross-platform compatible? I'd argue for at least the default to be the > latter, on the grounds that
I have no real opinion on this point; I was just saying that 'monotone ls unknown' should *never* die because of the name of any unknown file. If we can't print some filename as is, then we should escape characters in some appropriate way (handwaving here). When you try to 'monotone add' a file like that, it should perhaps disallow it (with some nicer error like 'monotone cannot handle control characters in filenames, not adding filename containing 0x07'), but again, shouldn't dump with an invariant triggered. thanks, -emile > a) Almost no-one really, really wants that file to be called that (as in > this case) > b) Otherwise, monotone gets to play fun games when it tries to check > that file out on a system that doesn't support that as a filename... > > -- > Jon Bright > Silicon Circus Ltd. > http://www.siliconcircus.com >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
