From: Tor Lillqvist Date: Tue, 9 Jan 2001 20:48:20 +0000 (+0000) Subject: Minor cosmetic change to previous ChangeLog entry. X-Git-Tag: GLIB_1_2_9PRE1~38 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=85537f0c8a434e04435b811d326b7516a63efb3e;p=platform%2Fupstream%2Fglib.git Minor cosmetic change to previous ChangeLog entry. --- diff --git a/ChangeLog b/ChangeLog index 9dbffb4..3f34a52 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-0 b/ChangeLog.pre-2-0 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-0 +++ b/ChangeLog.pre-2-0 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-10 b/ChangeLog.pre-2-10 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-10 +++ b/ChangeLog.pre-2-10 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-12 b/ChangeLog.pre-2-12 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-12 +++ b/ChangeLog.pre-2-12 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-2 b/ChangeLog.pre-2-2 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-2 +++ b/ChangeLog.pre-2-2 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-4 b/ChangeLog.pre-2-4 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-4 +++ b/ChangeLog.pre-2-4 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-6 b/ChangeLog.pre-2-6 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-6 +++ b/ChangeLog.pre-2-6 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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. diff --git a/ChangeLog.pre-2-8 b/ChangeLog.pre-2-8 index 9dbffb4..3f34a52 100644 --- a/ChangeLog.pre-2-8 +++ b/ChangeLog.pre-2-8 @@ -1,14 +1,13 @@ 2001-01-09 Tor Lillqvist - * giowin32.c (create_reader_thread): Rework the changes needed to - pass mainloop-test. Now we don't need to call TerminateThread() - after all, which is a relief, as the docs have a BIG RED WARNING - SIGN about using that API. Instead, when closing a fd channel that - has a reader thread running, just mark it as non-running and - additionally mark the fd as ripe for closing. When the reader - thread hopefully eventually gets something (and EOF or some actual - data), it will note that it shouldn't be running, break out of the - loop, and close the fd. + * giowin32.c: Rework the changes needed to pass mainloop-test. Now + we don't need to call TerminateThread() after all, which is a + relief, as the docs have a BIG RED WARNING SIGN about using that + API. Instead, when closing a fd channel that has a reader thread + running, just mark it as non-running and additionally mark the fd + as ripe for closing. When the reader thread hopefully eventually + gets something (and EOF or some actual data), it will note that it + shouldn't be running, break out of the 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.