This is an automated email from the ASF dual-hosted git repository.
lukaszlenart pushed a change to branch docs/releasing-struts-skill
in repository https://gitbox.apache.org/repos/asf/struts.git
discard 137cb0627 docs(skills): ship the stage and promote scripts with
releasing-struts
discard edb141600 docs(skills): add releasing-struts, the end-to-end release
runbook
omit b1aec6932 docs(skills): require plain-text list mail in the two
mail-producing skills
add 830d46a32 docs(skills): require plain-text list mail in the two
mail-producing skills (#1843)
add b953d8c9c docs(skills): add releasing-struts, the end-to-end release
runbook
add d700c5e30 docs(skills): ship the stage and promote scripts with
releasing-struts
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 (137cb0627)
\
N -- N -- N refs/heads/docs/releasing-struts-skill (d700c5e30)
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:
