This is an automated email from the ASF dual-hosted git repository.
grkvlt pushed a change to branch 1.0.0
in repository https://gitbox.apache.org/repos/asf/brooklyn-ui.git.
discard 4fa5a09 Merge pull request #169 from nakomis/1.0.0-cherry-picks
omit 395e21f Revert "allow relative path to parent to be configured"
discard 11588d8 Merge pull request #168 from nakomis/1.0.0-cherry-picks
omit 3897503 use the flattened pom so that revision is set correctly
omit c9a9026 Merge remote-tracking branch 'nakomis/fix-build' into 1.0.0
omit 4d84e4b Bumps npm, node, and webpack versions
new 81c8553 Bumps npm, node, and webpack versions
new 81f7617 use the flattened pom so that revision is set correctly
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 (4fa5a09)
\
N -- N -- N refs/heads/1.0.0 (81f7617)
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.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
