Skip to content
Snippets Groups Projects
Select Git revision
  • dd_area_choosers_common_refactor
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • 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

src

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    rswindell authored
    of the first message in the thread, or 0 if unknown (e.g. legacy message). When
    a new message is created, the thread_id value of the message being replied-to
    will be used, else if the new msg is not a reply, then the new message's number
    will be the value used for the thread_id.
    This "thread-id" feature (Deuce's idea) allows threads with a common parent to
    remain logically grouped after the original messages in the thread have been
    purged (though the original hiearchy will start to be lost).
    bdfe0f79
    History
    Name Last commit Last update
    ..