[Gnu-arch-users] [BUG] FEATURE PLANS: version messages

[Tom Lord]

  % tla set-message [--log LOG] [VERSION]
    Using LOG (or invoking $EDITOR, if necessary)
    perform an empty (no changes) commit to VERSION
    using LOG as the log message.

    The mangled log message will include a version
    variable setting:

        set-version-var: message-revision "REV"

        where REV is the name of this revision.


  % tla message [REVISION]

    Let MSGREV := tla version-var --from REV message-revision

    Then

       cat the log message for MSGREV


  % tla commit --message [....]

    Suppose that REV is the revision that this commit will
    create.

    Then the --message option makes this commit equivalent to:


        % tla set-version-var message-revision '"REV"'
        % tla commit [....]

    In other words, it's a normal commit that also sets 
    the version message.


------------------------------------------------------------

Category and Branch messages:

For every category, the latest log message of:

  cat--+category-message--0

is the category message.

For every branch, the latest log message of

  cat--branch+branch-message--0

is the branch message.

Commands such as:

  % tla set-message --category [--log LOG] [CATEGORY]
  % tla set-message --branch [--log LOG] [BRANCH]

should work.

-t