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

chaokunyang pushed a change to branch update_docs
in repository https://gitbox.apache.org/repos/asf/fory-site.git


 discard 5537b40f1b docs: use stable links for release guidance
 discard ab9f66a5da docs: fix navigation and deployment follow-ups
 discard 6526e0d553 docs: adopt capability-first documentation
     add b935368481 🔄 synced local 'docs/guide/' with remote 'docs/guide/'
     add 90a2d25f6e 🔄 synced local 'docs/guide/' with remote 'docs/guide/'
     add 946a244a60 🔄 synced local 'docs/specification/' with remote 
'docs/specification/'
     add e82a5072dd docs: adopt capability-first documentation
     add c267926ccf docs: fix navigation and deployment follow-ups
     add d71d189031 docs: use stable links for release guidance
     add f2e7ed9109 docs: fix legacy entry redirects

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   (5537b40f1b)
            \
             N -- N -- N   refs/heads/update_docs (f2e7ed9109)

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:
 src/plugin/redirect.js | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to