This is an automated email from the ASF dual-hosted git repository.

pkarwasz pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/logging-parent.git


 discard 87bf76c  Add `logging-parent` version `10.5.0` (RC3) website
 discard 79b0b9b  Add `logging-parent` version `10.5.0` (RC3) website
 discard d2683ca  Add `logging-parent` version `10.5.0` (RC2) website
 discard fb3e969  Add `logging-parent` version `10.5.0` website
 discard 98aebdf  Fix changelog
 discard 9f3b0d7  Update for `logging-parent` version `10.4.0` release
 discard 87981a4  Update files for RC3
 discard 407796e  Add `10.3.0` RC2 files, again
 discard e91c2eb  Add `10.3.0` RC2 files
 discard 2218ffa  Restore default profile
 discard 955d185  Replace HTML redirect with HTTP redirect
 discard f8eb09d  Add `logging-parent` version `10.3.0` website
 discard d22b491  Staging website is broken, using custom profile as a 
workaround
 discard c34cd95  Add release `10.2.0` website
 discard 77ae088  Revert to 'content'
 discard 11bc7c8  Add 'output' again
 discard 2820555  tried to remove output/content prefix in full
 discard d4536ba  content -> output
 discard 830ebd6  Add website-specific release instructions
 discard 4e01bfb  Add release `10.1.1` website
     add 31f28a5  Update `.asf.yaml` for `asf-site`
     add 5d224a1  Add release `10.1.1` website
     add fe3446b  Add website-specific release instructions
     add 3a92a31  Add `logging-parent` version `10.2.0` website
     add f7d2d83  Sync website with `main`
     add 2240a7b  Add `logging-parent` version `10.3.0` website
     add 2b474fa  Add `logging-parent` version `10.4.0` website
     add 52a99b9  Add `logging-parent` version `10.5.0` (RC3) website
     add 646fbbc  Sync `.asf.yaml` file between branches
     add cb27e77  Replace HTML redirect with HTTP redirect
     add 0d0aee7  Protect `asf-site` instead of `asf-staging`
     new 547b3b7  Version `10.6.0` RC 1

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   (87bf76c)
            \
             N -- N -- N   refs/heads/asf-staging (547b3b7)

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 1 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:
 .asf.yaml       |  25 +++++++++++++
 10.x/index.html | 108 ++++++++++++++++++++++++++++++++++++++++++++------------
 2 files changed, 110 insertions(+), 23 deletions(-)

Reply via email to