https://gitlab.synchro.net/main/sbbs/-/commit/9d359582c6c0e7ee06f6408f
Modified Files:
src/sbbs3/data.cpp
Log Message:
Timed event "month days" value of 1 means "any day" (same as 0)

This field should not normally have a value of '1' (no way to configure that, normally, since days are numbered starting at 1 and bit 1 is 2), but if it does, it's treated the same as 0 (any day of the month) - so fix that mismatch in getnexteventtime(). Just noticed this while comparing the logic with the new is_time_to_run() functions in main.cpp. That logic wasn't (should not have) changed, so this mismatch in the treatment of mdays == 1 existed before.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/197f7351542db704e4bfaf94
Modified Files:
src/sbbs3/data.cpp
Log Message:
Using mnemonic with @-codes for DoYouMeanThisUserQ text.dat string

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

src/sbbs3 data.cpp 1.31 1.32
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv16485

Modified Files:
data.cpp
Log Message:
Paranoia checks in getnextevent():
If either localtime_r() or mktime() return a error result, don't use use the non-sensical time.
Nelgin has reported that under some conditions, he sees:
Your time has been reduced due to an upcoming event on Wed Dec 31 1969 18:00:00 when using Ctrl-T (time info hot key).
I don't have an explanation for this, but if either of those function calls failed in getnextevent(), something like this could happen. <shrug>


---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net