[
https://issues.apache.org/jira/browse/SVN-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169317#comment-16169317
]
Chad Sterling commented on SVN-4698:
------------------------------------
Thanks,
Sorry about that, missed that part about the mailing list. Good luck with
the product.
Chad
On Sun, Sep 17, 2017 at 5:49 AM Johan Corveleyn (JIRA) <[email protected]>
> Comment thread on revision
> --------------------------
>
> Key: SVN-4698
> URL: https://issues.apache.org/jira/browse/SVN-4698
> Project: Subversion
> Issue Type: New Feature
> Components: svnserve
> Affects Versions: 1.9.0
> Environment: Any supported configuration of subversion.
> Reporter: Chad Sterling
> Priority: Trivial
>
> There are times when new information about a commit is discovered after the
> fact. Trivial cases of this are empty commit messages or forgotten line items
> on a commit. However at times it may be discovered that a certain change had
> an unintended side effect, or that the change has other features that are
> worth documenting.
> One current solutions to this problem are to use a third party tool to allow
> discussion which has the downside that when the repository is moved the
> useful documentation is lost/disconnected, and the comment thread is not
> default viewable when logs are queried from the repository.
> A second option is to allow log messages to be edited after the fact which
> has the consequence that historical commits can no longer be considered
> immutable, as the log messages can be erased or changed to have a different
> meaning.
> What is suggested would be to allow a comment thread to be attached to the
> log such that developers could have a conversation about a particular commit
> without altering the original log message.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
