X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;ds=sidebyside;f=lib%2Frsc;h=25dc9f6624d8b4684adc8197ea652fa7467f772e;hb=12e136332a7dcb6e4d0b4a85fef9ff97dfa57200;hp=248ce0ff5a12b2a5880f4897b01e9ce6fb775336;hpb=ce38e57e97b39b0cde532ff6a83b8881de6d2f3a;p=plan9front.git

diff --git a/lib/rsc b/lib/rsc
index 248ce0ff5..25dc9f662 100644
--- a/lib/rsc
+++ b/lib/rsc
@@ -192,3 +192,56 @@ I'm not trying to write the last word.
 I'm sorry, but I disagree.
 Nice debugging.
 I'm sorry but I don't exactly understand.
+Do you have evidence that this is important and that your change would help?
+We're still struggling with this. My apologies.
+All the CLs are reviewed, right?
+Let's move on.
+Sorry, but it's too late.
+If I had more free time I would port C++ and Java to Plan 9 just to annoy you.
+Honestly, it looks like a compiler bug.
+I do understand that many people are confused.
+Let's write tutorials and improve diagnostics.
+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.
+How easily can you write a test?
+We broke the rule, and we shouldn't have. Our bad.
+ML is indeed a fantastic language for writing compilers.
+We can't keep the code running indefinitely.
+Have you filed a bug about this?
+Thanks for letting us know.
+Why?
+I'm sorry you are insulted and distressed by this.
++golang-nuts bcc golang-dev
+This looks pretty O(N^2) to me
+If you want to discuss that proposal, please do it on the Reddit post, not here.
+You said you were going to write some benchmarks.
+Is anyone else having a hard time getting through all.bash on Sierra?
+Please don't.
+You are speaking like a compiler author instead of a user.
+Just make sure to use an identifying User-Agent line when you make requests from your back end.
+I don't want ordinary users to be making choices about "how much debug info is enough".
+Thanks for letting us know.
+This doesn't seem worthwhile.
+It only works when we're in the process of preparing a release.
+Yes, and we need to fix that.
+Sorry, but no.
+It's been two hours since that fix landed.
+I needed that last week.
+I have a new blog post you might be interested in.
+Ever since I wrote “go get,” we on the core Go team hoped the community would take care of dependency management.