On Thu, Jul 13, 2006 at 01:17:39PM -0700, Zack Weinberg wrote:
Currently the knowledge of which characters are not allowed in a
pathname is split between paths.cc and constants.cc.
paths.cc:has_bad_chars is the sole user of
constants.cc:illegal_path_bytes, but adds more to the set (notably
Nathaniel Smith wrote:
You might try asking on the list? I haven't set up a buildslave under
windows, but other people have...
Sure.
The first problem I had is that twistd doesn't find the win32 reactor,
but I guess that is not a problem afterall, under Cygwin the default
ones should work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Yes, indeed seems that sqlite's os.h treats Cygwin as a WIN build
instead of a UNIX one.
Just removing the __CYGWIN__ case from sqlite/os.h seemed to resolve
the problem.
But the are locking issues indeed.
filemon's output:
On Sat, Jul 15, 2006 at 11:41:01AM +0200, Lapo Luchini wrote:
Lapo Luchini wrote:
Yes, indeed seems that sqlite's os.h treats Cygwin as a WIN build
instead of a UNIX one.
Just removing the __CYGWIN__ case from sqlite/os.h seemed to resolve
the problem.
But the are locking issues indeed.
On Thu, Jul 13, 2006 at 12:25:40AM -0700, Nathaniel Smith wrote:
On Tue, Jul 11, 2006 at 03:38:38AM -0700, Nathaniel Smith wrote:
Now that we have diff -p support on mainline, is there any reason we
shouldn't make it the default?
[...]
So, umm, given that no-one has raised any objections...
In net.venge.monotone.contrib.benchmark rev
679ea52924887e816903342104f797ba9c0be6d4
when I run:
#!/bin/sh
rm -rf myscratch myresults
python2.4 benchmark.py \
-m mtn-0.27=/home/anderse/projects/monotone/tar-0.27/mtn \
-b
When I attempt to pull from venge.net, if I don't have any key
specified in my _MTN/options file, everything works fine. If I have a
key specified, then I get:
mtn: connecting to venge.net
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:13977 | 26 |
On Sat, 2006-07-15 at 17:42 -0700, Eric Anderson wrote:
When I attempt to pull from venge.net, if I don't have any key
specified in my _MTN/options file, everything works fine. If I have a
key specified, then I get:
mtn: connecting to venge.net
mtn: finding items to synchronize:
mtn:
[meant to go to the list, sorry Tim.]
The protocol should maybe grow SMTP-style machine interpretable code
numbers at the beginning of the human readable strings?
zw
On 7/15/06, Timothy Brownawell [EMAIL PROTECTED] wrote:
On Sat, 2006-07-15 at 17:42 -0700, Eric Anderson wrote:
When I attempt
