Reword my last ChangeLog entry a bit.

This commit is contained in:
Tor Lillqvist 2004-09-25 20:34:16 +00:00
parent 780c013db4
commit 627f9b3350
5 changed files with 25 additions and 25 deletions

View File

@ -1,10 +1,10 @@
2004-09-22 Tor Lillqvist <tml@iki.fi>
* glib/gmessages.c: [Win32] Don't open a console window if
standard output or standard error are invalid (as they are for GUI
applications). These console windows that open up unexpectedly
have caused endless amounts of confusion among
end-users. (#141102, #151175)
* glib/gmessages.c: [Win32] Don't ever open a console
window. (Which we used to do if standard output or standard error
are invalid, as they are for GUI applications.) These console
windows that open up unexpectedly have caused endless amounts of
confusion among end-users. (#141102, #151175)
Don't output the process id on Windows. Only output the program
name. If not set with g_set_prgname(), fetch the application

View File

@ -1,10 +1,10 @@
2004-09-22 Tor Lillqvist <tml@iki.fi>
* glib/gmessages.c: [Win32] Don't open a console window if
standard output or standard error are invalid (as they are for GUI
applications). These console windows that open up unexpectedly
have caused endless amounts of confusion among
end-users. (#141102, #151175)
* glib/gmessages.c: [Win32] Don't ever open a console
window. (Which we used to do if standard output or standard error
are invalid, as they are for GUI applications.) These console
windows that open up unexpectedly have caused endless amounts of
confusion among end-users. (#141102, #151175)
Don't output the process id on Windows. Only output the program
name. If not set with g_set_prgname(), fetch the application

View File

@ -1,10 +1,10 @@
2004-09-22 Tor Lillqvist <tml@iki.fi>
* glib/gmessages.c: [Win32] Don't open a console window if
standard output or standard error are invalid (as they are for GUI
applications). These console windows that open up unexpectedly
have caused endless amounts of confusion among
end-users. (#141102, #151175)
* glib/gmessages.c: [Win32] Don't ever open a console
window. (Which we used to do if standard output or standard error
are invalid, as they are for GUI applications.) These console
windows that open up unexpectedly have caused endless amounts of
confusion among end-users. (#141102, #151175)
Don't output the process id on Windows. Only output the program
name. If not set with g_set_prgname(), fetch the application

View File

@ -1,10 +1,10 @@
2004-09-22 Tor Lillqvist <tml@iki.fi>
* glib/gmessages.c: [Win32] Don't open a console window if
standard output or standard error are invalid (as they are for GUI
applications). These console windows that open up unexpectedly
have caused endless amounts of confusion among
end-users. (#141102, #151175)
* glib/gmessages.c: [Win32] Don't ever open a console
window. (Which we used to do if standard output or standard error
are invalid, as they are for GUI applications.) These console
windows that open up unexpectedly have caused endless amounts of
confusion among end-users. (#141102, #151175)
Don't output the process id on Windows. Only output the program
name. If not set with g_set_prgname(), fetch the application

View File

@ -1,10 +1,10 @@
2004-09-22 Tor Lillqvist <tml@iki.fi>
* glib/gmessages.c: [Win32] Don't open a console window if
standard output or standard error are invalid (as they are for GUI
applications). These console windows that open up unexpectedly
have caused endless amounts of confusion among
end-users. (#141102, #151175)
* glib/gmessages.c: [Win32] Don't ever open a console
window. (Which we used to do if standard output or standard error
are invalid, as they are for GUI applications.) These console
windows that open up unexpectedly have caused endless amounts of
confusion among end-users. (#141102, #151175)
Don't output the process id on Windows. Only output the program
name. If not set with g_set_prgname(), fetch the application