This is an automated email from the ASF dual-hosted git repository.
jinrongtong pushed a change to branch 4.9.x
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
discard 6ee8d0718e [4.9.x] Promptly return a response when the validation
parameters cannot be modified (#7849)
add f011fe0cd9 Revert "[maven-release-plugin] prepare for next development
iteration"
add a6e912d42f Revert "[maven-release-plugin] prepare release
rocketmq-all-4.9.8"
add ee652df9a0 Promptly return a response when the validation parameters
cannot be modified
add 2bdd53ef66 [maven-release-plugin] prepare release rocketmq-all-4.9.8
add 1aa9aa095f [maven-release-plugin] prepare for next development
iteration
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (6ee8d0718e)
\
N -- N -- N refs/heads/4.9.x (1aa9aa095f)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
acl/pom.xml | 2 +-
broker/pom.xml | 2 +-
client/pom.xml | 2 +-
common/pom.xml | 2 +-
distribution/pom.xml | 2 +-
example/pom.xml | 2 +-
filter/pom.xml | 2 +-
logging/pom.xml | 2 +-
namesrv/pom.xml | 2 +-
openmessaging/pom.xml | 2 +-
pom.xml | 2 +-
remoting/pom.xml | 2 +-
srvutil/pom.xml | 2 +-
store/pom.xml | 2 +-
test/pom.xml | 2 +-
tools/pom.xml | 2 +-
16 files changed, 16 insertions(+), 16 deletions(-)
