You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2019/08/05 07:18:00 UTC
[jira] [Commented] (SLING-8606) Wrong JIRA ticket ref contained in
commit message to SLING-6398
[ https://issues.apache.org/jira/browse/SLING-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899829#comment-16899829 ]
Robert Munteanu commented on SLING-8606:
----------------------------------------
Hi [~angela]. Thanks for spotting this, it is indeed a wrong reference. Unfortunately I can not change the commit message anymore as
- our SVN repository is read-only
- I cannot change commits that already went through in Git
The only thing that comes into my mind is to add a note about this issue to the description of SLING-6368. This way the correct issue would be easier to find. Would that work for you?
> Wrong JIRA ticket ref contained in commit message to SLING-6398
> ---------------------------------------------------------------
>
> Key: SLING-8606
> URL: https://issues.apache.org/jira/browse/SLING-8606
> Project: Sling
> Issue Type: Wish
> Components: Repoinit
> Reporter: angela
> Priority: Minor
>
> [~rombert], when fixing SLING-6398 in https://svn.apache.org/repos/asf/sling/trunk@1774410 , the following commit message was added:
> {quote}
> SLING-6368 - Repoinit should not attempt to create access control entries when no changes are needed
> {quote}
> as you can see this references the wrong JIRA ticket, which makes i a bit hard to find out why the given changes was introduced.... you may already suspect, that i am not all convinced the code is behaving correctly (see separate ticket that will follow) ;)
>
> anyway: if there was any chance to fix the commit message, i would appreciate it.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)