# 
# 
# patch "ChangeLog"
#  from [119afa4105552991f39a4c436abeebf876e44ca8]
#    to [73c944d692818567a5920ba6deec9a4ab18b8782]
# 
# patch "tests/t_database_sig_cleanup.at"
#  from [69faa2185c168dfa6769da545b4a308f8ddd28dd]
#    to [931a30f59821cd4244a3d005a688002e88cd01bf]
# 
============================================================
--- ChangeLog	119afa4105552991f39a4c436abeebf876e44ca8
+++ ChangeLog	73c944d692818567a5920ba6deec9a4ab18b8782
@@ -1,3 +1,9 @@
+2005-12-05  Matthew Gregan  <address@hidden>
+
+	* tests/t_database_sig_cleanup.at: Mark this as NOT_ON_WIN32; as
+	per the MSDN link I've added to the test, we can't handle
+	SIGINT/SIGTERM gracefully on Windows.
+
 2005-12-04  Nathaniel Smith  <address@hidden>
 
 	* paths.cc (file_path): MM() the path we're validating.
============================================================
--- tests/t_database_sig_cleanup.at	69faa2185c168dfa6769da545b4a308f8ddd28dd
+++ tests/t_database_sig_cleanup.at	931a30f59821cd4244a3d005a688002e88cd01bf
@@ -1,9 +1,15 @@
 #  -*- Autoconf -*-
 
 AT_SETUP([database is closed on signal exit])
 
 MONOTONE_SETUP
 
+# SIGTERM and SIGINT can't really be handled on Win32:
+# http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_CRT_signal.asp
+# We also don't attempt to install handlers for them in main.cc, but there's
+# little point given the discussion at the MSDN link above.
+NOT_ON_WIN32
+
 # this test checks that .db-journal files aren't left lying about if the 
 # process is killed with SIGTERM or SIGINT