#pentagram@irc.freenode.net logs for 22 Jan 2008 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:13:38] <-- watt has left IRC ()
[00:47:25] --> watt has joined #pentagram
[00:47:25] --- ChanServ gives channel operator status to watt
[00:50:26] <-- watt has left IRC (Read error: 104 (Connection reset by peer))
[00:52:53] --> watt has joined #pentagram
[00:52:53] --- ChanServ gives channel operator status to watt
[00:55:41] --> watt_ has joined #pentagram
[00:55:41] <-- watt has left IRC (Read error: 104 (Connection reset by peer))
[00:57:41] --> watt has joined #pentagram
[00:57:41] --- ChanServ gives channel operator status to watt
[00:57:41] <-- watt_ has left IRC (Read error: 104 (Connection reset by peer))
[00:59:23] --> watt_ has joined #pentagram
[00:59:23] <-- watt has left IRC (Read error: 104 (Connection reset by peer))
[01:00:27] --> watt has joined #pentagram
[01:00:27] --- ChanServ gives channel operator status to watt
[01:00:27] <-- watt_ has left IRC (Read error: 104 (Connection reset by peer))
[01:02:57] --> watt_ has joined #pentagram
[01:15:59] <watt_> Anyone else see what looks like portscans from 85.190.0.3
[01:17:14] <watt_> Whatever computer it is has an http server responding on it with this message: "If you see portscans/abuse from 85.190.0.3 Please read http://freenode.net/policy.shtml#proxies "
[01:19:25] <-- watt has left IRC (Read error: 110 (Connection timed out))
[01:23:29] <-- watt_ has left IRC ()
[01:23:43] --> watt has joined #pentagram
[01:23:43] --- ChanServ gives channel operator status to watt
[01:41:42] <watt> Ok... according to the folks at #freenode its a bot that scans you everytime you connect.
[01:42:24] <watt> and I guess my connection bounces a bit more than I'd like.
[02:00:09] --> watt_ has joined #pentagram
[02:02:19] <-- watt_ has left #pentagram ()
[02:03:23] --> watt__ has joined #pentagram
[02:07:12] --> watt___ has joined #pentagram
[02:07:13] <-- watt__ has left IRC (Read error: 104 (Connection reset by peer))
[02:15:17] <-- watt has left IRC (Read error: 110 (Connection timed out))
[12:12:02] --> Mrrrr has joined #pentagram
[12:22:40] <-- Mrrrr has left IRC ()
[12:34:52] --> Mrrrr has joined #pentagram
[12:55:33] <-- Mrrrr has left IRC (Read error: 110 (Connection timed out))
[13:50:40] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[14:07:30] <-- watt___ has left IRC ()
[14:42:43] --> watt has joined #pentagram
[14:42:43] --- ChanServ gives channel operator status to watt
[14:54:48] --> Mrrrr has joined #pentagram
[17:28:54] <watt> I hate make. A space in a path name just caused the automated build here at work to blow up on me
[17:30:14] <wjp> not enough quotes somewhere?
[17:30:49] <watt> dirs=$(dir $(wildcard */.svn))
[17:31:15] <watt> $(MAKE) -w -j $(dirs)
[17:31:33] <watt> basically - its a bit more complicated than that
[17:32:36] <watt> wildcard function expands the paths without quotes, making it look like two entries instead of one.....
[17:32:58] <watt> and even the rules based on the dir names won't work either.
[17:37:24] <wjp> hm
[17:38:21] <wjp> doesn't seem like there are any real ways around that
[17:39:55] <watt> yeah - I think I'll have to just force people under threat of violence not to put spaces in the names of paths under the top level directory.
[17:55:05] <watt> been having all sorts of issues with automated build lately - mostly due to the lack of consistent unix tools used in our windows environment.
[17:55:23] <watt> Multiple versions of make, rm, cp.. etc
[17:56:31] <watt> all of which seem to have one annoying issue or another (like some versions of cp and network shares, for instance)
[19:51:41] --> Kazin has joined #pentagram
[21:56:59] <-- Kazin has left IRC (Read error: 110 (Connection timed out))
[23:13:16] --> Kirben has joined #pentagram
[23:13:16] --- ChanServ gives channel operator status to Kirben
[23:57:07] <-- watt has left IRC ()