I wish to ask two rather fundemental questions regarding TKLBAM:

1. To what extent does TKL support today the annotation of an individual TKLBAM backup (with, say, the current revision-level of the project, or a short summary of what has changed since the last backup)?
   • I found a way to add such annotations using the Webmin interface:
     System -> Backup and Migration (TKLBAM) -> View Log -> {individual backup} -> "Action Details" : "Log entry annotation"
      
   • Feature-request: the ability to somehow specify this annotation up-front, using the Webmin interface and/or the TKLBAM command-line.
      
   • Feature-request: the ability to somehow see this annotation when listing the current set of backups (in the Hub, the Webmin interface, and using the tklbam-list command-line)
2. Does TKLBAM provide any way to "fork" the backup history?
   • My current understanding is that once tklbam-init is invoked for a given server-instance, a unique (simple integer) "Backup ID" is created and permanently assigned to that instance.  Moreover, each individual tklbam-backup that is subsequently invoked appends another backup to the simple, linear, list of backups associated with that ID.
      
   • Is there any way today to extend this linear scheme with support for forks and branches?  If not, can you please record my feature-request?
     • Bonus: maybe the "Backup ID" could be changed from a simple integer to a "dotted-revision-number", that could also capture the "branching lineage" of any individual backup?