In the sortm warning message, say "file modification time"

instead of "file mtime", per Paul F.'s suggestion.

diff --git a/test/folder/test-sortm b/test/folder/test-sortm
index 930b0581b457a40efce754dc38f26ff8f18bfda2..0753ecb0f4d90f404c29c20b1bc5a93881758149 100755 (executable)
--- a/test/folder/test-sortm
+++ b/test/folder/test-sortm
@@ -388,7 +388,7 @@ check "$expected" "$actual"
 
 # check -check
 cat >"$expected" <<EOF
-sortm: can't parse date field in message 14, will use file mtime
+sortm: can't parse date field in message 14, will use file modification time
 sortm: errors found, no messages sorted
 EOF
 
@@ -437,7 +437,8 @@ EOF
 
 sed -e 's/Sep//' $MH_TEST_DIR/Mail/inbox/7 > $MH_TEST_DIR/Mail/inbox/14
 run_test 'sortm -check -nocheck' \
-         "sortm: can't parse date field in message 14, will use file mtime"
+         "sortm: can't parse date field in message 14, will use file \
+modification time"
 scan >"$actual"
 check "$expected" "$actual"
 

diff --git a/uip/sortm.c b/uip/sortm.c
index 28e2bd64d9be0f9a9b7d3e04eca7025e0ea46b8b..677a86fbd483cf849dcdc566b0ccfc044c967295 100644 (file)
--- a/uip/sortm.c
+++ b/uip/sortm.c
@@ -423,7 +423,9 @@ get_fields (char *datesw, int msg, struct smsg *smsg)
     if (!datecomp || (tw = dparsetime (datecomp)) == NULL) {
        struct stat st;
 
-       advise (NULL, "can't parse %s field in message %d, will use file mtime",
+       advise (NULL,
+               "can't parse %s field in message %d, "
+               "will use file modification time",
                datesw, msg);
        fstat (fileno (in), &st);
        smsg->s_clock = st.st_mtime;