This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch feature/CAMEL-24713-doc-samples-mojo
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 2de10b4e21fa CAMEL-24713: camel-jbang - document camel_catalog_sample
in the MCP server page
discard 7839fef25ca3 CAMEL-24713: camel-jbang - generate the
camel_catalog_sample fallback (eip-samples.json) from the documentation with a
mojo, validated in the build
add f9b35ff05a83 CAMEL-24713: oncompletion.adoc - the YAML prose names the
executorService option like its example
add b0840ab6b362 CAMEL-24713: camel-jbang - generate the
camel_catalog_sample fallback (eip-samples.json) from the documentation with a
mojo, validated in the build
add a9d8dacbf914 CAMEL-24713: camel-jbang - document camel_catalog_sample
in the MCP server page
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 (2de10b4e21fa)
\
N -- N -- N refs/heads/feature/CAMEL-24713-doc-samples-mojo
(a9d8dacbf914)
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:
docs/user-manual/modules/ROOT/pages/oncompletion.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
