2014-02-25 18:41 UTC+0100 Viktor Szakáts (vszakats users.noreply.github.com)
  * include/hbsetup.ch
  * utils/hbmk2/hbmk2.prg
    * switching to more dynamic and streamlined mode; This fork will now
      by a rule NOT define the next HB_LEGACY_LEVEL* while in development.
      It means that deprecated stuff will get deprecated right away.
      (Unless someone is explicitly enabling these using HB_USER_CFLAGS.
      Not recommended because deprecated stuff will not be maintained
      or supported.)
      The real turning point now is when code protected by HB_LEGACY_LEVEL*
      is actually deleted from source tree. This should happen typically
      on a stable release or after a reasonable timespan since the
      introduction of said legacy level. When that happens, users can
      copy the deleted parts to their projects and continue maintaining
      it there (or adapt code to not require them of course).
    * deleted HB_LEGACY_OFF setting, since it is the default now.
    ; In this fork this commit effectively means that HB_LEGACY_LEVEL5
      will get disabled.