00:03
<ezyang>
How painful is it to change all refs on google code from one email address to another?
00:03
<ezyang>
I want to ditch my old google code account, but my html5lib bits are still on it
01:13
karlcow
wonders what is happening with David Storey
01:13
<karlcow>
http://twitter.com/dstorey/status/6035181550
01:13
<karlcow>
>I'm announcing now I'm leaving Opera. They like to be the good gu nut that is 100% bull shit.
01:27
<roc>
perhaps someone hacked his account
01:28
<karlcow>
roc: that could be a possibility indeed.
01:45
<Hixie>
othermaciej: is there a list of pending deadlines for change proposals?
01:45
<othermaciej>
Hixie: I'm working on one and will post it by tomorrow - all current due dates are either Dec 3 or Dec 17 I believe
01:46
<othermaciej>
Hixie: specifically I think Dec 3 might be the date for counter-proposals for the "split Microdata" issue
01:49
<Hixie>
k
01:49
<Hixie>
i'm drowning in e-mail from my vacation, so i was worried about missing something
01:55
<othermaciej>
there was quite a bit of public-html email recently
02:00
<Hixie>
i noticed
02:00
<Hixie>
bbiab
02:08
<TabAtkins>
othermaciej: That list would be awesome - I was asking around for one a day or two ago, because I wanted to write some counterproposals.
02:11
<othermaciej>
all right, let me see if I can throw one together quickly
03:47
<othermaciej>
Hixie: are you around?
03:47
<Hixie>
yup
03:48
<Hixie>
othermaciej: what's up?
03:49
<othermaciej>
Hixie: is this sufficiently detailed and informative to be a Change Proposal, in your opinion: http://lists.w3.org/Archives/Public/public-html/2009Nov/0153.html
03:49
<othermaciej>
I assume it is intended to be for ISSU-56 urls-webarch
03:49
<Hixie>
i think a change proposal is unnecessary for that topic, since the editor hasn't rejected anything yet as far as i'm aware
03:50
<Hixie>
in fact quite the opposite
03:51
<othermaciej>
I didn't think so either (though technically we do have an ISSUE, but it seems like one we could resolve it by amicable resolution assuming you now have what's needed)
03:52
<Hixie>
i don't yet have what's needed; the change proposal's first sentence is "assuming those requirements are met", which they aren't yet
03:52
<Hixie>
so the change proposal similarly isn't ready to be considered yet
03:52
<Hixie>
i don't think there's anything controversial here
03:53
<othermaciej>
if the requirements are not met, could you reply with specifics?
03:53
<othermaciej>
I'm looking at this because I'm trying to complete the issue status page
03:53
<Hixie>
the iri working group doesn't exist yet
03:53
<Hixie>
the requirements are to be met by the iri working group
03:54
<Hixie>
i'm sure larry and i will work together over the coming months to address the issues
03:54
<othermaciej>
ok
03:54
<Hixie>
i don't think anything process-related needs to be invoked yet
03:54
<othermaciej>
I'm a little confused about what Larry intended with his proposal
03:55
<Hixie>
i dunno
03:56
<othermaciej>
since I'm making the list, I don't want to just drop that one on the floor
03:57
<othermaciej>
I'm not sure if he's asking to reference algorithms that are not yet defined in an IRIBIS draft, if he thinks everything needed is defined already, or if this proposal is intended to be considered once the relevant IETF WG forms and the draft is in a suitable state
03:58
<Hixie>
the latter, i think, given the first sentence
03:58
<othermaciej>
you mean the last of my options?
03:58
<Hixie>
yeah
04:02
<othermaciej>
wow, the draft charter calls for WG LC by January 2010
04:04
<Hixie>
IRI?
04:04
<Hixie>
the htmlwg charter calls for WG LC by June 2008, so I don't know that charters mean much
04:05
<othermaciej>
so, I have a table giving status and next applicable deadline for issues going through the Change Proposal process
04:06
<othermaciej>
trying to figure out where to post it
04:06
<othermaciej>
I'm not sure if the HTML WG wiki is sufficiently flexible about formatting
04:06
<Hixie>
doesn't it have an html mode?
04:09
<othermaciej>
the wiki's table support does headers as a <td><p><strong>... instead of a <th>
04:11
<Hixie>
nice
04:12
<othermaciej>
I guess I'll just check it into cvs
04:19
<othermaciej>
Hixie, TabAtkins: http://dev.w3.org/html5/status/issue-status.html
04:24
<othermaciej>
Hixie: does that contain all the info about deadlines and such that you need?
04:25
<Hixie>
it would be ideal for my purposes if it was sorted by deadline, but yes, that's awesome
04:25
<othermaciej>
I left out the ISSUE-56 thing for now but I may add it depending on Larry's response
04:26
<Hixie>
(td, th { vertical-align: top; } would be nice also)
04:27
<othermaciej>
oh, I forgot issue-7
04:27
<othermaciej>
I'll add that style change too
04:35
Hixie
is tempted to just say yes to bugs 8365 and 8368 and see what happens
04:41
<othermaciej>
removing section 6 would break the spec pretty bad
04:43
<othermaciej>
section 8 could probably be removed or split without undue hassle, but it is one of the few HTML5 features implemented by all the browsers
04:43
<Hixie>
i'm tired of people filing bugs that are fantastically bad ideas (like those two)
04:43
<othermaciej>
(or at least the postMessage part is if I recall correctly)
04:44
<Hixie>
and then being bitched at when i say "no"
04:44
<Hixie>
so i think i might just say "yes" and be bitched at for that instead
04:44
<Hixie>
if those bugs are still open by the time i get to them
04:45
<Hixie>
it would be a nice change
04:45
<othermaciej>
has anyone complained about a bug resolution lately (other than to escalate to the tracker)?
04:46
<Hixie>
i havne't done anything lately
04:46
<Hixie>
so no
04:46
<othermaciej>
I assume Shelley filed these so she could make an ISSUE of them
04:46
<othermaciej>
the last instance I recall of someone getting upset over a negative resolution was a summary-related bug where John Foliot was unhappy
04:47
<othermaciej>
that was in September, before the official bureaucratic process
04:59
Hixie
stares at 136 e-mails on xml in html and sighs
04:59
<Hixie>
do i have to read this all
05:16
<GPHemsley>
Hixie: Was that a rhetorical question?
05:20
<GPHemsley>
Hixie: Because, if not, I'll say no. Just to see what happens. ;)
05:51
<Hixie>
i read it after all
05:54
<TabAtkins>
I knew you would.
05:54
<TabAtkins>
Unrelated: how was your vacation?
06:01
<Hixie>
relaxing.
06:01
<Hixie>
i wrote the beginnings of a MUD using WebSockets
06:07
<TabAtkins>
Interesting.
08:45
Philip`
wonders if it is safe to prophesy that the bugs about removing sections from the spec will be closed as WONTFIX and then escalated as issues and then the whole discussion can start all over again on the mailing list for a month and then start again when there's a vote and then it will be rejected
08:49
<hsivonen>
Philip`: maybe. and the Process will have cost a lot in terms of time of the employees and contractors of W3C Member companies.
08:52
<hsivonen>
othermaciej: thanks for fixing the Change Proposal timetable
08:52
<othermaciej>
hsivonen: thanks for pointing out the bug
08:54
<hsivonen>
Hixie: why does the 'table scope' algorithm name 'html in the HTML namespace' specifically?
08:55
<Hixie>
no idea
08:55
<hsivonen>
hmm. I see the spec has qualified the 'in scope' algorithms with "in the HTML namespace"
08:55
<hsivonen>
I wonder if that's a necessary qualification
08:56
<hsivonen>
hmm. maybe it is, because the MathML HTML containers aren't scoping
08:56
<hsivonen>
like foreignObject
08:56
<hsivonen>
sigh
08:57
<hsivonen>
Hixie: is it by design, that the 'in scope' algorithms aren't sensitive to the local names in the MathML or SVG namespaces for legacy content magic?
08:57
<Hixie>
no idea
08:58
<Hixie>
i have paged that algorithm to long term memory at the moment
08:58
hsivonen
wonders if the interesting local names break out of foreign lands anyway
08:58
<hsivonen>
maybe I should make a note to check if the namespace check can be optimized away
10:22
<hsivonen>
sigh. krijnh missed the interesting data
10:23
<othermaciej>
he needs a better connection!
10:23
<othermaciej>
want me to repaste it?
10:24
<jgraham>
http://dev.opera.com/articles/view/mama-phrase-block-list/ suggests <spacer> is more popular than <blink>
10:25
<hsivonen>
othermaciej: I can rephrase for my bug reports, so no need to repaste
10:25
<othermaciej>
as long as there's a permanent record
10:26
<hsivonen>
jgraham: is that counting tags or pages?
10:27
<hsivonen>
hmm. WBR is more rare than SPACER according to MAMA
10:31
<hsivonen>
looks like Adobe GoLive 4 has generated <spacer> elements
10:32
<jgraham>
hsivonen: Not sure
10:32
<jgraham>
I think tags
10:34
<jgraham>
Actually given the most popular elements are all roughly as frequent as pages it must be pages
10:34
<jgraham>
s/as/as there are/
10:35
<webben>
hsivonen: you've probably already seen this, but in case you haven't, more grist for the dtds-as-single-point-of-failure mill at http://support.microsoft.com/kb/973687
10:36
<hsivonen>
webben: I hadn't seen that one. thanks
10:39
<MikeSmith>
hsivonen: see final comment at http://bugzilla.validator.nu/show_bug.cgi?id=640#c7
10:40
<hsivonen>
MikeSmith: doesn't 'redundant' mean that the language was previously registered but the same string can be derived from the new registration system by other means?
10:40
<MikeSmith>
yeah, that is what it means, afaik
10:41
<MikeSmith>
but there are some cases in the registry where those redundant entries are also marked as deprecated
10:41
<MikeSmith>
so even though they are derived tags, I guess what they are saying is, don't use them
10:42
<hsivonen>
ah ok
10:42
<hsivonen>
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=531030
10:42
<hsivonen>
I'll file a spec bug if it gets WONTFIXed
10:42
<hsivonen>
afk
10:43
MikeSmith
hopes that now these changes are committed, he will not have to spend any time studying the IANA language tag registry again for a long. long time
10:58
<Philip`>
othermaciej: The page with the list of pages is two years old, so the pages probably changed
10:58
<Philip`>
The newer data seems to indicate a similar percentage usage
11:31
<hsivonen>
Hixie: wouldn't it be a safe bet to parse <spacer> as a void element even if non-Gecko browsers didn't support it in layout
11:32
<hsivonen>
Hixie: after all, the rendering section is optional but the parsing section is mandatory
11:51
<gsnedders>
Is there any reason why outerHTML isn't on Node?
11:51
<gsnedders>
Well, I guess it doesn't make sense on Document and DocumentFragment
11:51
<gsnedders>
and innerHTML doesn't make sense on comment/ProcessingInstruction/DocumentType
11:54
<smaug_>
or on Attr node :)
11:55
<jgraham>
Attr node doesn't make much sense :)
11:58
<Dashiva>
outerHTML: Element, innerHTML: Element, Document, DocumentFragment?
11:58
<hsivonen>
is the 'table text' insertion mode there only because Hixie didn't want to spec an explicit accumulation buffer for all insertion modes?
11:59
<jgraham>
hsivonen: Yes
11:59
<hsivonen>
jgraham: thanks. I think I'll leave it out
11:59
<hsivonen>
unless I later find I need it for SAX correctness or something
12:03
<hsivonen>
Hixie: why doesn't 'form' in 'in table' inspect the form pointer (and ignore the token if the form pointer is non-null)?
12:04
<hsivonen>
Hixie: and why doesn't 'form' in 'in table' set the form pointer?
12:28
gsnedders
is now mixing up Python and Javascript when he tries to write Python. Gah.
12:30
<Philip`>
They're similar enough that that should cause less problems than mixing up many other pairs of languages
12:32
<Dashiva>
I mix in Japanese when I try to speak German
12:58
<gsnedders>
Hixie: I've been told to tell you.
13:03
<payman>
gsnedders: I assumed u would try to find out _what_ to tell Hixie!
13:07
<gsnedders>
payman: I thought you could just tell him yourself though :P
13:10
<payman>
gsnedders: You didn't, otherwise you wouldn't ping him at all.
13:11
<gsnedders>
Philip`: Until you hit things like foo = { a: b }, which has very different meanings
13:12
<jgraham>
Not that different
13:12
<gsnedders>
Different enough to cause errors in Python
13:12
<Philip`>
Just use foo = { "a": b } everywhere
13:15
<Philip`>
I quite like how Perl uses the => operator to automatically quote the word on its left
13:15
<gsnedders>
eww, Perl
13:15
<Philip`>
so { a => $b } is equivalent to { 'a', $b }
13:15
<Philip`>
and (pack LL => 123, 456) is equivalent to (pack 'LL', 123, 456) etc
13:16
<jgraham>
This must be some new meaning of the word "like" that I don't understand
13:17
<Philip`>
It seems better than the autoquotiness being dependent on further-removed syntax like whether you're inside a {...} declaration
13:17
<Philip`>
and better than it being indistinguishable from a block of code containing a label and an expression
13:18
<jgraham>
What's wrong with just putting in quote characters?
13:20
<Philip`>
Putting in quote characters is a fine alternative
13:20
<Philip`>
TIMTOWTDI
13:21
<jgraham>
(BSOTAUCAHTR)
13:21
<jgraham>
(But Several Of Those Are Unnecessarilly Confusing And Hard To Read)
14:03
<webben>
hsivonen: http://code.google.com/p/google-web-toolkit/issues/detail?id=2069 claims to be FIXED - is the compiled JS mentioned at http://blog.whatwg.org/html5-live-dom-viewer now hosted online somewhere?
14:05
<hsivonen>
webben: http://livedom.validator.nu/
14:08
<webben>
hsivonen: ta
14:22
<gsnedders>
Anyone know of a good Java tutorial?
14:24
<zcorpan>
http://lmgtfy.com/?q=good+Java+tutorial
14:25
<murr4y>
the official sun one, tbh
14:25
gsnedders
notes Google isn't a very recommendation engine
14:26
gsnedders
could Google, "Good music", and hate all of it
14:26
<zcorpan>
google sucks
14:26
<gsnedders>
Yeah, Bing ftw!
14:27
<hsivonen>
"good Foo tutorial" is a hard question, because people who'd be competent to review if a tutorial on Foo is bogus have been doing Foo long enough not to read tutorials
14:27
<zcorpan>
bing actually has sun's java tutorial at #1
14:27
<jgraham>
http://letmebingthatforyou.com/?predicate=good%20java%20tutorial
14:27
<Philip`>
I had "Teach Yourself Java in 21 Days", but I can't recommend it since it took about five years before I learnt Java
14:28
<hsivonen>
Philip`: I had roughly the same experience
14:28
<jgraham>
So it was wrong by a factor of almost 90
14:28
<jgraham>
Impressive
14:29
<gsnedders>
I wonder who did the QA on the book
14:29
<gsnedders>
I guess the problem is you need a new QA for which draft, as they know Java by the end of it... hopefully.
14:29
<hsivonen>
speaking of books and QA, Zeldman did ask for reviews: http://www.zeldman.com/2009/11/23/reviewers-needed/
14:29
<zcorpan>
Philip` wouldn't have bought it at all and thus never learned java if it said "Teach Yourself Java in 38325 Days"
14:30
<Philip`>
I think the book started with a Hello World applet which seemed to require far too much code and too many tools, so I went back to QuickBASIC
14:30
<Philip`>
hsivonen: Amazon reviews, not technical reviews
14:31
<zcorpan>
s/38325/1825/
14:32
<hsivonen>
http://norvig.com/21-days.html
14:32
<jgraham>
The intent of the two seems quite different...
14:32
<Philip`>
(It's easier to get started if you don't do applets, because then the only inexplicable magic is the "public static void main(String[] args)" bit which you can safely ignore for a few weeks)
14:33
<hsivonen>
the mistake *everything* about early Java did (books included) was talking about applets
14:35
<Philip`>
zcorpan: You're forgetting leap years
14:35
<zcorpan>
Philip`: yeah, i know
14:35
<Philip`>
Also, it might have been seven years
14:41
<hsivonen>
speaking of Learn X in y amount of time, I just got spam advertising learning Chinese in 16 minutes and Spanish in 6 minutes.
14:42
<jgraham>
heh
14:45
<gsnedders>
They blatantly think you have leet langauge skillz
15:06
<hsivonen>
Hixie: Why is there "Script data end tag open state"? Wouldn't it be equivalent to go directly to "Script data end tag name state"?
15:07
<hsivonen>
(and moving the buffer creation and token creation one step backwards)
15:09
<hsivonen>
Hixie: the state naming is inconsistent with "close tag" and "end tag"
15:09
<hsivonen>
the new script state machine sure has states...
15:12
<gsnedders>
It was great fun to implement.
15:16
<zcorpan>
it's worse than doctypes
15:27
<hsivonen>
I hope the zapping of the comment-like escapes from noframes, noscript and iframe is ok...
15:28
<karlcow>
I'm curious to know how henri defines "on the Web" in the comment http://www.w3.org/Bugs/Public/show_bug.cgi?id=8365#c15
15:28
<karlcow>
Does that mean going through HTTP?
15:28
<zcorpan>
hsivonen: i researched that (sent to list), only style is a bit problematic but i couldn't find a way to make style less problematic
15:29
<Philip`>
Wow, someone fixed lists.w3.org so previous/next message links into different date ranges work
15:29
<danbri>
:) at last
15:29
<Dashiva>
Now they just have to fix rel=next
15:30
<zcorpan>
hsivonen: see http://www.w3.org/mid/op.u2crntvwidj3kv⊙sl (and followups)
15:31
<karlcow>
epub used on the Web - http://www.epubbooks.com/blog/20080718/bookworm-reader-for-epub-books/
15:31
<hsivonen>
zcorpan: thanks
15:31
<karlcow>
another interesting (hack) usage of HTML5 video in epub http://blog.threepress.org/2009/11/15/using-html5-video-in-epub/
15:32
<hsivonen>
karlcow: browsable from any Internet host using an unextended Web browser
15:32
<zcorpan>
hsivonen: apparently the encoding issue was with Philip`'s decoder and not with v.nu's sniffer
15:32
<hsivonen>
karlcow: where a Web browser is a piece of software suitable for browsing the Web
15:33
<hsivonen>
karlcow: or you know it's a Web browser when you see one :-)
15:33
<karlcow>
that would include ftp :)
15:34
<hsivonen>
karlcow: if SPDY is adopted, would SPDY-enabled sites be on the Web?
15:34
<karlcow>
no idea according to your Web definition which is not testable.
15:35
<hsivonen>
karlcow: it's a circular definition
15:35
<hsivonen>
this has been discussed before
15:35
<karlcow>
CQFD
15:37
<hsivonen>
karlcow: anyway, the notion that a section needs to be split out because allegedly some use of HTML doesn't need the section is bogus
15:37
<Philip`>
Can we remove accessibility since graphical UAs don't need most of it?
15:39
<karlcow>
maybe an exit strategy of this issue is to rephrase the section in a way which makes it independent of "browser". It would be possible for example to call it "HTML User agent" or something similar
15:39
<zcorpan>
Philip`: why would graphical UAs not need accessibility?
15:40
<hsivonen>
karlcow: trying to define the Web is like trying to define obscenity
15:40
karlcow
has a joke wrt this last sentence of hsivonen but will abstain
15:40
<hsivonen>
karlcow: but when an off-line file is loaded to a non-browser ebook reader app, you know it's not a Web use
15:41
<karlcow>
too many negatives in that sentence
15:42
<zcorpan>
when an online file is loaded to a browser app, you know it's a Web use
15:42
<hsivonen>
karlcow: anyway, the whole ePub thing is a red herring, because even if ePub were in charter scope, it doesn't follow that we should split out stuff that ePub allegedly doesn't need
15:43
<Philip`>
zcorpan: (I mean a graphical UA with a user who just looks at the screen, and doesn't use any tools that can make use of ARIA and doesn't right-click to see longdesc and doesn't disable images to see alt text etc)
15:43
<Philip`>
Is there a list of non-streamable HTML errors somewhere?
15:43
karlcow
wonders if hsivonen is then the big wolf jumping of red herrings :)
15:43
<hsivonen>
Philip`: There's a public-html email of mine
15:43
karlcow
is trying to imagine hsivonen with a costume
15:44
Philip`
is trying to imagine karlcow making sense :-p
15:45
<karlcow>
Philip`: it is what you get when you discuss with poets or dreamers!
15:45
<karlcow>
we need more mythology in HTML 5 WG.
15:45
<karlcow>
wait maybe we do ;)
15:46
<zcorpan>
Philip`: isn't it just attributes on stray <html>, attributes on stray <body>, stuff between </head> and <body> that should be moved to head, some cases for aaa, foster parent, and stuff after </body> and </html>?
15:47
karlcow
thought about little red hood when reading red herring
15:47
<shelleyp>
Philip: Graphical UAs do "need" accessibility, as a way of providing alternative content for visual impaired
15:48
<timz>
Can anybody tell me if there is any particular reason why the blank Nodes of triples generated by this parser http://james.html5.org/microdata/ begin with 54 ? as in _:vmrahSFh54. and not for example _:vmrahSFh1. and then _:vmrahSFh2.
15:50
<shelleyp>
exit
15:50
<shelleyp>
Sorry, wrong command in wrong place
15:51
<Philip`>
timz: The names are meaningless and just an implementation detail of the RDF serialiser it uses
15:51
<jgraham>
timz: The triples are generated by some python rdf library
15:51
<timz>
Ok thanks
15:51
<jgraham>
(well the serializations are, the actual content is my fault)
15:52
<jgraham>
(and I think the content is buggy so don't depend on it for anything remotely important)
15:52
<jgraham>
(but do report bugs when you find them)
15:53
<timz>
jgraham: the triples or the html content ?
15:53
<jgraham>
The triples
15:53
<timz>
okay
15:53
hsivonen
notes that the WG name doesn't have a number
15:53
<jgraham>
As in I think the microdata -> RDF conversion is broken
15:54
<hsivonen>
HTML WG (no number) and XHTML2 WG (with number)
15:54
<jgraham>
The microdata -> JSON is more likely to be right but is also probably broekn
15:54
<timz>
wel bugs, the ntriple parser doesn't handle item as property value very well
15:54
<timz>
euh n3
15:54
<timz>
i mean
15:54
<Philip`>
zcorpan: I'm happy to assume it's just that, since I can't think of any others and can't find hsivonen's email
15:55
<Philip`>
hsivonen: And the XHTML2 WG's output has largely been updates to XHTML1
15:56
<hsivonen>
Philip`: http://lists.w3.org/Archives/Public/public-html/2009May/0582.html
16:03
<Philip`>
hsivonen: Aha, thanks
16:03
<karlcow>
[11:01] <hsivonen> HTML WG (no number) and XHTML2 WG (with number)
16:03
<karlcow>
short memory
16:03
<karlcow>
xhtml2 wg was html wg.
16:04
<karlcow>
in the reorganization, renaming, etc scenario
16:04
<karlcow>
The naming has been part of the things falling into the cracks I guess.
16:33
<Dashiva>
http://support.microsoft.com/kb/973687
16:35
<Philip`>
Dashiva: Old news
16:35
<Philip`>
http://krijnhoetmer.nl/irc-logs/whatwg/20091125#l-282
16:37
<Dashiva>
:(
16:39
<Philip`>
Old news is better than no news, so don't be sad
16:39
<Dashiva>
I'm sad because I missed the first posting
18:41
<zcorpan_>
i hope microsoft have flipped the whitespace switch in MSXML in IE before shipping xhtml support
18:47
<Philip`>
zcorpan_: Better write some test cases for them to make sure they get it right
18:50
<zcorpan_>
Philip`: feel free to add a tc to https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=489112
19:02
<saikatc>
hey guys, i'm using pisa html to pdf converter, which i believe uses html5lib under the hood, and I'm noticing that images in my html are not being converted properly. these images are using data uris whose source point to base64 encoded pngs. is it possible that html5lib doesn't support this, or does it seem like i should be looking elsewhere for the cause of this problem?
19:03
<saikatc>
by not converted properly, i mean, aren't showing up at all =)
19:03
<gsnedders>
elsewhere
19:03
<gsnedders>
html5lib does nothing but create a tree
19:04
<saikatc>
i see, thanks
20:29
<othermaciej>
Hixie: ayt?
22:08
<Huvet>
Hi again! I just ran 295 swedish news sites through html5lib, and here are the stats: 3 Bug 126, 2 Bug 128
22:10
<Huvet>
if I just catch AttributeError and ValueError, all of them pass :)
22:12
<jgraham>
Huvet: Great
22:12
<jgraham>
I gues I can glance at the bugs now, but it is really time to sleep
22:12
<Huvet>
yep, that's a far better track record than all others I've tried
22:13
jgraham
is pretty disappointed we fail so often
22:14
<Huvet>
bah, you're the best :)
22:14
<Huvet>
but I wouldn't mind you passing them all ;)
22:46
<jgraham>
Huvet: I think I have fixes for both those bugs. Just need to make a testcase for 126
22:56
<jgraham>
Huvet: changes pushed