This is an automated email from the ASF dual-hosted git repository.
jdaugherty pushed a change to branch shadowJarLicensing
in repository https://gitbox.apache.org/repos/asf/grails-core.git
discard 71c0d99f03 chore: #14886 add licensing & notice files for grails-cli
shadowJar
discard 8618cc169d chore: #14886 add licensing plugin to grails-forge
discard bcded8bfc5 chore: #14886 add notice for Jakarta API usage for
grails-core
new 6aec78a848 chore: #14886 add notice for Jakarta API usage for
grails-core
new a340c0753a chore: #14886 add licensing plugin to grails-forge
new ec7f6e8beb chore: #14886 add licensing & notice files for grails-cli
shadowJar
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 (71c0d99f03)
\
N -- N -- N refs/heads/shadowJarLicensing (ec7f6e8beb)
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 3 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:
NOTICE | 3 +++
1 file changed, 3 insertions(+)
