Minor cosmetic change to previous ChangeLog entry.

ChangeLog

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-0

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-10

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-12

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-2

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-4

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-6

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.

ChangeLog.pre-2-8

@@ -1,14 +1,13 @@
 2001-01-09  Tor Lillqvist  <tml@iki.fi>
 
-	* giowin32.c (create_reader_thread): Rework the changes needed to
+	* giowin32.c: Rework the changes needed to pass mainloop-test. Now
-	pass mainloop-test. Now we don't need to call TerminateThread()
+	we don't need to call TerminateThread() after all, which is a
-	after all, which is a relief, as the docs have a BIG RED WARNING
+	relief, as the docs have a BIG RED WARNING SIGN about using that
-	SIGN about using that API. Instead, when closing a fd channel that
+	API. Instead, when closing a fd channel that has a reader thread
-	has a reader thread running, just mark it as non-running and
+	running, just mark it as non-running and additionally mark the fd
-	additionally mark the fd as ripe for closing. When the reader
+	as ripe for closing. When the reader thread hopefully eventually
-	thread hopefully eventually gets something (and EOF or some actual
+	gets something (and EOF or some actual data), it will note that it
-	data), it will note that it shouldn't be running, break out of the
+	shouldn't be running, break out of the loop, and close the fd.
-	loop, and close the fd.
 
 	The socket channel closing code should probably be changed
 	similarily, but that will have to wait until I have a test case.