From ffd23297ae1e769177275b1dc533930ff3eca50a Mon Sep 17 00:00:00 2001
From: "tgauth@bu.edu" <tessgauthier@microsoft.com>
Date: Thu, 7 Sep 2023 16:59:04 -0400
Subject: [PATCH] add comments

---
 misc.c               | 7 +++++++
 regress/test-exec.sh | 6 +++---
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/misc.c b/misc.c
index 0d676c2d8..1177fcb2b 100644
--- a/misc.c
+++ b/misc.c
@@ -331,6 +331,13 @@ waitfd(int fd, int *timeoutp, short events, volatile sig_atomic_t *stop)
 	pfd.fd = fd;
 	pfd.events = events;
 #ifdef WINDOWS
+	/*
+	 * Windows does not support sigprocmask
+	 * which was implemented to handle ctrl+c during multiplexing.
+	 * When Win32-OpenSSH adds multiplexing support, modify and use
+	 * native_sig_handler in contrib/win32/win32compat/signal.c here
+	 *
+	*/
 	for (; !have_timeout || *timeoutp >= 0;) {
 		monotime_tv(&t_start);
 		r = poll(&pfd, 1, *timeoutp);
diff --git a/regress/test-exec.sh b/regress/test-exec.sh
index 7ac3306b2..24c5c1a2b 100644
--- a/regress/test-exec.sh
+++ b/regress/test-exec.sh
@@ -302,8 +302,8 @@ fi
 SSHLOGWRAP=$OBJ/ssh-log-wrapper.sh
 # BALU todo - check if we need to pass -T flag
 if [ "$os" == "windows" ]; then
-# timestamp line messes up stderr-data.sh stderr-after-eof.sh, 
-# seems to be used for concurrency tests that Windows doesn't support yet anyway
+# timestamp line messes up stderr-data.sh stderr-after-eof.sh 
+# seems to be used for debugging concurrency tests (a feature unsupported on Windows currently)
 cat >$SSHLOGWRAP <<EOD
 #!/bin/sh
 logfile="${TEST_SSH_LOGDIR}/\${timestamp}.ssh.\$\$.log"
@@ -317,7 +317,7 @@ EOD
 else
 cat >$SSHLOGWRAP <<EOD
 #!/bin/sh
-#timestamp="\`$OBJ/timestamp\`"
+timestamp="\`$OBJ/timestamp\`"
 logfile="${TEST_SSH_LOGDIR}/\${timestamp}.ssh.\$\$.log"
 echo "Executing: ${SSH} \$@" log \${logfile} >>$TEST_REGRESS_LOGFILE
 echo "Executing: ${SSH} \$@" >>\${logfile}