Commits


fossil: fix EOF detection when reading 9P message When the 9P connection is closed, reads on the connection will keep returning 0. So, fossil ends up looping forever, trying to read a 9P message, consuming 100% CPU. The fix interprets 0 bytes read as EOF. Reproduce by killing the 9pserve process serving the fossil service, or by listening on tcp and using 9p(1).


fossil: required p9p changes R=rsc https://codereview.appspot.com/13352057


fossil: move from liboventi to libthread and libventi R=rsc https://codereview.appspot.com/13504049


fossil: import from plan 9 R=rsc https://codereview.appspot.com/7988047