This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a change to branch fix-jbang-metadata-mojo
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 506b03a96302 Resolve picocli completion candidates and add missing
import
omit 61c35cc32c7c Merge remote-tracking branch 'origin/main' into
fix-jbang-metadata-mojo
omit d902a90cae2e Fix JBang metadata generation to detect all commands
add c9ac60daf2f3 Fix docs gulp race condition with dsl target directories
add 3ec45dc4c7a5 Add resilient ENOENT handling for parallel build races
add c2480ac1c940 Fix JBang metadata generation to detect all commands
add 0b80621ab254 Resolve picocli completion candidates and add missing
import
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 (506b03a96302)
\
N -- N -- N refs/heads/fix-jbang-metadata-mojo (0b80621ab254)
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/gulpfile.js | 43 ++++++++++++++++++++++++++++++++++++++++---
1 file changed, 40 insertions(+), 3 deletions(-)
