I think we're done here.
I think you have to drag it into the Applications folder.
I ran Plan 9 from Bell Labs as my day to day work environment until around 2002.
+Let's focus on what's there.
+If the Plan 9 group had had its way, Plan 9 would have been released for free under a trivial MIT-like license (the one used for other pieces of code, like the one true awk) in 2003 instead of creating the Lucent Public License. Or in 2000 instead of creating the "Plan 9 License". Or in 1995 instead of as a $350 book+CD that came with a license for use by an entire "organization". Or in 1992 instead of being a limited academic release.
+Code freeze on March 1 does not mean "break everything the day before March 1".
+Godoc is a relatively small program. It is built from 102 packages built from 582 source files.
+does anyone understand why the dragonfly builder times out connecting to localhost during run.bash?
+We've entered the feature freeze.
+We're far from stable right now.
+it would be nice to be able to try the plan 9 go port without a plan 9 system.
+is anyone willing to put together a plan 9 qemu image with mercurial set up and a go tree checked out and ready to build?
+okay.
+sounds worth trying
+I'd like to keep the discussion here about Windows 2000 support in general and not about the technical details of this specific problem.
+But that is just a guess.
+RFC 3339 is very clear about this.
+Thanks.
+It is just not worth the effort.
+Hello there. Has anyone written a vt100 emulator for Plan9? Thanks.
+Much better to spend time reading and learning from the code than blogging about what's wrong with the local variable names.
+I would prefer to arrange that the output is useful.
+Nice.
+No one googles local variable names.
+This is not a step forward.
+the opposite of brevity is length, not clarity.
+Impressive.
+Great.
+Does this happen to anyone else?
+has anyone written an smb client for plan 9?
+has anyone written a mac hfs file system srv?
+has anyone added midi support to devaudio?
+Comments, suggestions welcome.
+never mind then.
+Great bug, thanks.
+I replied on golang-nuts.
+There is no issue here.
+I'm not sure if this distinction is a valid one.
+I'd rather not.
+Oops.
+Not that I have any real definitive answer, but I can hazard a guess...
+That makes sense.
+I don't remember seeing that happen ever before.
+i don't look at build failures at all anymore because they are all false positives.
+Grumble grumble.
+I don't remember the last time I saw a sam-fans message.
+I'll fix it.
+working as intended; please don't file an issue.
+sure
+I would love it if someone would create a well-tested emacs Go module.
+Honestly it sounds like you have not written any Go programs.
+I'm not convinced this needs to be in the standard library.
+I haven't thought about it yet.
+Don't do that.
+Don't overthink this.
+I don't know what you are arguing for or against.
+We understand your point of view.
+Thanks for letting us know.
+It happened.
+i do not want to support a linux/amd64p32 port right now.
+No. I've answered this before.
+If this isn't solved soon I think we should turn off commit access for everyone.
+Very small changes can still contain very large bugs.
+I don't intend to try to fix rc.
+That's fine.
+This is a serious mistake.
+I am going to be away for the rest of the week.
+At the risk of sounding pedantic, package url is not an http server.
+don't worry about it.
+You can't make everything faster all the time.
+Thanks.
+Please just wait.
+I haven't logged into a real Plan 9 system in many years
+I did not promise it was going to happen.
+Please don't.
+no.
+I just did
+The docs are incorrect.
+Where you see a hack I see an elegant design.
+For now you just have to fight the temptation.
+Just for comparison, godoc is 16 MB on my laptop.
+In general, for me, the answer to whether there is a problem depends on how complex the solutions are.
+what's going on with freebsd-386, plan9-386, and plan9-amd64?
+All our arm builders seem to have disappeared.
+Please stop.
+what's going on with freebsd-386, plan9-386, and plan9-amd64?
+All our arm builders seem to have disappeared.
+Please stop.
+Yes, it is intentional.
+No, please do NOT do this.
+Why does http://build.golang.org/perf say 'Error: no commits'?
+You're designing a tool. Stop.
+Let's start with a wiki page.
+This is almost certainly noise.
+It's done; move on.
+Thanks but no thanks.
+I filed the bug that change fixed.
+I will fix this.
+It sounds reasonable to me.
+Thanks for your patience.
+LGTM (not actually looking carefully)
+I'd like to disable more than just the test.
+swtch.com is in the process of moving to the cloud.
+Yes, there have been many ad-hoc solutions.
+Sure.
+That's fun.
+I want to echo what Rob said.
+It's just a mistake.
+Yes, absolutely. I agree with you 100%.
+This scenario is definitely confusing.
+It's 2015. Why do terminal programs interpret 1970s escape codes instead of html? You'd think by now 'echo <b>bold</b>' would work.
+What happened to build.golang.org?
+I think I'm missing something.
+The outline below is my attempt at a skeleton for a streamlined version of the proposal proposal.
+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.
projects / plan9front.git / blobdiff