You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2022/07/29 09:15:36 UTC
[GitHub] [activemq-artemis] archlevel opened a new pull request, #4158: in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client
archlevel opened a new pull request, #4158:
URL: https://github.com/apache/activemq-artemis/pull/4158
in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [activemq-artemis] jbertram closed pull request #4158: in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client
Posted by GitBox <gi...@apache.org>.
jbertram closed pull request #4158: in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client
URL: https://github.com/apache/activemq-artemis/pull/4158
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [activemq-artemis] gemmellr commented on pull request #4158: in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client
Posted by GitBox <gi...@apache.org>.
gemmellr commented on PR #4158:
URL: https://github.com/apache/activemq-artemis/pull/4158#issuecomment-1199088788
As with your other PR I dont see any actual useful change here, simply merging existing commits. If you have some changes you should add those to your own branch and raise a PR from it.
You should raise a JIRA for an issue you are looking to address, and then reference it in the commit message (see: most previous commits).
PRs should also target main unless first discussed otherwise, not branches like 2.23.x, as fixes will be picked from main where appropriate. There almost certainly wont be any more 2.23.x releases though as 2.24.0 is almost out, perhaps even late today, having been under release vote for a couple of days already.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org