discard 7435440 Removed JenkinsFile since it used by the runtime repo now
discard 4a69441 chore(refactor): Fixes #470, moved camel-k-runtime into his own repo
discard 528aae4 Removed runtime folder
new 631de4f Removed runtime folder
new 350ab11 chore(refactor): Fixes #470, moved camel-k-runtime into his own repo
new ac265fa Removed JenkinsFile since it used by the runtime repo now
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 (7435440)
N -- N -- N refs/heads/jenkins-pr-merge-job (ac265fa)
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 533 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.