Skip to content
Snippets Groups Projects

Repository graph

You can move around the graph by using the arrow keys.
Select Git revision
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • c23-playing
  • cryptlib-3.4.7
  • dailybuild_linux-x64
  • dailybuild_macos-armv8
  • dailybuild_win32
  • dd_file_lister_filanem_in_desc_color
  • dd_msg_reader_are_you_there_warning_improvement
  • hide_remote_connection_with_telgate
  • master default protected
  • mingw32-build
  • mlong/darkmodetweak
  • mode7
  • new_config_format
  • new_file_base
  • new_user_dat
  • ree/mastermind
  • revert-9d6b6c2f
  • rip_abstraction
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results
Created with Raphaël 2.2.016Nov151615141312111098976545432130Oct3130292829282726252625262524232223222120191817161514131211101110532130Sep2928Don't overwrite the offset with the IMAP offset, add a new one.Use fmutex_open for 100% locking and auto-removal upon close/terminationDon't overwrite the posted-reply FTN REPLY ID if it was provided by the clientLook up referenced FTN MSGID of messages being POSTed and use in FTN-REPLYWrap each cleanup step in a separate try/catch in exit func.Replace / with - in group/sub namesLeave the user/*.ftp lock file open for better protectionPrint the correct .ini filename where ptrs are savedOverhaul the saved config.Some saved_config cleanup before splitting configs.Don't download more msgs than the max for the sub-board (if non-zero)We can call remove() right after opening to enable auto-remove on *nixMake the spamblock.cfg auto-added entries expirable (configurable duration)Just a little wording update on the fmutex file open log messageFix for Borland C++ buildUse fmutex_close() and don't log ENOENT errors when removing pack*.now filesAdd fmutex_close() method to atomically remove the mutex file on Win32Add a sanity check on saved config.More speed optimizationsUse fmutex_open() instead of fmutex() to better protect the pack*.lock filesAdd fmutex_open() for cases where you want to keep the mutex file openThe progress reports (e.g. "[ Done 100.0% ]") should never go to logsUse sopen(... SH_DENYRW) for fmutex() instead of open()Don't rollback scan pointer on sub close.What I hope are the last \Seen and \Recent fixes.Remove set-but-never-used msg_ptrsReolve !ERROR 2 (No such file or directory) removing "data/pack####.now"Use timestr() instead of ctime_r() for logging full date/timesSimplify close_sub()If open_sub() fails, set readonly to true.Save scan_ptr for all subs in config.More Seen flag overhaul.Roll the epoch back to zero if it hits 9007199254740991Fix BODYSTRUCTURE bug that prevented macOS Sequoia from loading messagesRemove "QWK Prepack" feature (has been on chopping block for a long time)sbbs_t::fremove() will now, by default, ignore (not log) ENOENT errorsUpdates nightly builds in filebaseReturn 1 on failure (e.g. authentication failure), not 0Detect hung event_thread and log detailsLog event command-lines (repeating event code was redundant)