fortunes: ./configure CFLAGS="-I$HOME/source/harvey/ape/amd64/include -I$HOME/source/harvey/ape/include -mno-red-zone -ffreestanding -fno-builtin -nostdlib -trigraphs -D_SUSV2_SOURCE -D_POSIX_SOURCE -D_LIMITS_EXTENSION -D_BSD_SOURCE -D_BSD_EXTENSION -DHAVE_SOCK_OPTS -DHARVEY -DPlan9" LDFLAGS="-static $HOME/source/harvey/ape/amd64/lib/crt1.o $HOME/source/harvey/ape/amd64/lib/crti.o $HOME/source/harvey/ape/amd64/lib/crtn.o -L$HOME/source/harvey/ape/amd64/lib -L$HOME/source/harvey/amd64/lib" LIBS="-lbsd -lap -lc" LIBM="" --prefix=$HOME/source/harvey/ape/ports *--host=x86_64-linux-gnu --build=x86_64-harvey *--enable-shared=no

lib/rob

@@ -334,3 +334,21 @@ I support the idea of unrecorded talks.
 We do not accept patches
 Syntax highlighting is juvenile.
 Working as designed.
+I've written programs with twenty implementations of io.Reader inside.
+Who cares? Shut up.
+What is wrong with my analysis?
+I just want to explain something.
+I recommend in the strongest terms that you don't do this.
+Sockets are the X windows of IO interfaces.
+Ignore what I wrote.
+In other words, here's how to do it but don't do it.
+I did indeed.
+I don't understand what you mean by 'reset'.
+I am, and as far as I can tell it makes no difference whatsoever.
+Please put this silly objection to rest. It has no merit.
+Interpretations will vary.
+I think the pattern used well is perfectly acceptable in certain situations.
+Like everything that attracts scrutiny, the key point is to use the idea well: safely, clearly, correctly, and only when appropriate.
+I am not trying to be difficult, but you must understand it's not simple to address your question.
+One step at a time.
+Thanks for grinding through those.

lib/rsc

@@ -205,3 +205,17 @@ Thank you for writing a 3rd party tool.
 It's true that there are no plans yet, but I think it's also true that we need to start planning.
 Yes, that's confusing.
 Please do not spend time on this.
+Maybe this is true, but I haven't seen it.
+The fundamental design question here is whether the benefit outweighs the complexity being added.
+Enough with the religion. Please.
+It should just work.
+Sorry for not replying earlier. I don't really know.
+Great.
+This seems OK.
+Let's take our time and do it right (whatever that is).
+Really we're just behind on triaging bugs.
+I'll dig the code up and post it somewhere. I never made it truly usable.
+Will follow up off list.
+Wait a second.
+I think it's always been this way.
+I would wait until there's a more established pattern of a problem before introducing additional mechanisms.

lib/theo

@@ -522,3 +522,48 @@ There are too few of us, we cannot take on every problem.
 Everyone, please ignore these trolls who are cross-posting.
 Essentially, you are on your own. :-)
 I am not so sure.
+obviously.
+I don't know, but I'll think about it later, because I am busy.
+So the original idea wasn't yours.  And now you think it can't work.  And you are still talking about it.  I see.  Very interesting.
+That statement is full of potential for misunderstanding, and cannot be left alone.
+I was wrong.
+Thanks.
+Careful there :-)
+That is incorrect advice for the OpenBSD world.
+Your mistake.
+This bug report totally sucks.
+what is "this case"?
+my advice: walk away from this one.
+Generally Unix has no way of doing this.
+So what do you really mean here?
+Is a crash a performance impact?
+what is the goal?
+Your emails only contain opinions.
+words words words words
+Are you done?
+Doesn't that send shivers down your spine?
+Your bug report is too incomplete.  Can't help you.
+No.
+We'd rather jump off a cliff.
+Good luck with that.
+Looking forward to you providing code which solves the problem.
+This feature is probably older than you.
+it is behaving *exactly* as intended.
+There are a few compromises.
+I think I know a perfect candidate to take this further: You.
+Seriously?
+The OpenBSD process is quite well understood.  Use the best methods, doubt what you do, refractor.
+Hey, it looks like you are just trying to be a dick.
+Does your mother know?
+It's great that you have an opinion.
+Run something else! We don't care!
+That's a load of bull.
+Your opinions count for zero.
+To achieve merit, you must do the homework you assigned yourself.
+Get serious.
+and I wanna build a rocket ship...
+No thanks.
+The problem is obvious.
+If you don't have the skill to do it, well that's too bad...
+You didn't do your homework, and it blew up in your face.  Then you wrote a few paragraphs.  Then I replied.  That is the whole sad story.
+I tried to read the rest of what you wrote. It makes no sense.

lib/troll

@@ -229,3 +229,15 @@ Subject: [golang-dev] vendoring the stdlib
 [harvey-commits] [PATCH 2/2] Compile Harvey in C11 mode.
 [harvey] we need to bring sam back
 [harvey] booting a disk
+[Harvey] Harvey broken for me
+[harvey] Cannot boot with QEMU
+[harvey] we don't have a repeatable build process
+[harvey] Git clone not working
+[harvey] today's broken build
+[9fans] need a REAL WORKING iso
+[harvey] There is interest in harvey here at the riscv workshop
+[harvey] gerrit hell
+[harvey] Harvey fails to boot in qemu
+[golang-dev] godoc.org is down
+[harvey-commits] chdir regression test
+[harvey] FOSDEM

sys/games/lib/fortunes

@@ -5197,3 +5197,17 @@ It would be a cute trick to set up some sort of temporary compiler environment w
 I did take a look at rewriting the CoC in Basic English and found it way too restrictive. -- Andrew Gerrand
 [#OpenBSD] Carefully explaining your problem is half the solution.
 If you get this, delete it. - Sorry! -- Tim Berners-Lee, www-talk, Mon, 28 Oct 91 14:34:12 GMT+0100
+Why are you wasting my life? -- Jeff Bezos
+All operating systems are bullshit. -- Ted Unangst
+If you want to get started with autotools, try to build yourself a minimal autotools project. Once you have a working stub, you already took the biggest hurdle. -- Hacker News comment
+Please, excuse me the outflow.
+uriel, what you say would make sense if the "jokes" didn't include putting mein kampf in /lib. -- erik quanstrom
+ISIS Influence on Web Prompts Second Thoughts on First Amendment
+Whenever possible, you should use the 'cat' command line tool for this. Here's an example in Go:
+GCC 6 Will Warn You About Misleading Code Indentations
+Subject: [FD] Apple WatchOS v2.1 - Denial of Service Vulnerability
+Any objections to me rewriting rc in go without all known bugs? -- brucee
+One way that I was able to get this working was forking 9front and adding a clunk callback to Srv structure.
+Your Go installation is broken. -- Brad Fitzpatrick
+./configure CFLAGS="-I$HOME/source/harvey/ape/amd64/include -I$HOME/source/harvey/ape/include -mno-red-zone -ffreestanding -fno-builtin -nostdlib -trigraphs -D_SUSV2_SOURCE -D_POSIX_SOURCE -D_LIMITS_EXTENSION -D_BSD_SOURCE -D_BSD_EXTENSION -DHAVE_SOCK_OPTS -DHARVEY -DPlan9" LDFLAGS="-static $HOME/source/harvey/ape/amd64/lib/crt1.o $HOME/source/harvey/ape/amd64/lib/crti.o $HOME/source/harvey/ape/amd64/lib/crtn.o -L$HOME/source/harvey/ape/amd64/lib -L$HOME/source/harvey/amd64/lib" LIBS="-lbsd -lap -lc" LIBM="" --prefix=$HOME/source/harvey/ape/ports *--host=x86_64-linux-gnu --build=x86_64-harvey *--enable-shared=no
+Apache is less magical than it was in the 90's. -- Brad Fitzpatrick