The Graph displays the log graph (“history”) starting from the
selected Branches anchors. Branches/tags and other refs will show
up at the “appropriate” commits. In case of File (or Subtree) Logs or
filtered Logs (see Filter input field, below), every ref will be
mapped to the most recent commit of the graph which is still part of the
ref’s history. In case of File (or Subtree) Logs, the file (or subtree)
content of the mapped ref commit will be identical to the content of the
actual commit to which the refs points. For filtered Logs, there is no
such relation between the mapped commit and the actual commit, still you
will be able to see which of your filtered commits are part of which
ref’s history.
Mapped refs which are not exactly located at the commit to which they are attached will be denoted by ~.
The Graph can be customized in many ways from the Options-menu
(≡).
You can customize your graph window clicking on "hamburguer buttom" in the top right corner of that window
https://docs.syntevo.com/SmartGit/Latest/Log.html :
Graph view
The Graph displays the log graph (“history”) starting from the selected Branches anchors. Branches/tags and other refs will show up at the “appropriate” commits. In case of File (or Subtree) Logs or filtered Logs (see Filter input field, below), every ref will be mapped to the most recent commit of the graph which is still part of the ref’s history. In case of File (or Subtree) Logs, the file (or subtree) content of the mapped ref commit will be identical to the content of the actual commit to which the refs points. For filtered Logs, there is no such relation between the mapped commit and the actual commit, still you will be able to see which of your filtered commits are part of which ref’s history. Mapped refs which are not exactly located at the commit to which they are attached will be denoted by
~
.The Graph can be customized in many ways from the Options-menu (≡).