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

jan pushed a change to branch feat/3.x/otp23
in repository https://gitbox.apache.org/repos/asf/couchdb.git.


 discard 7cd3f9b  chore: simplify version detection h/t @vatamane
 discard 95b24b8  chore: update dependency pointers to release tags
 discard de511fb  feat: somewhat hacky version detection
 discard 94766ce  feat: update deps to support otp23 in a full build
 discard 4d75411  feat: work around get_stacktrace deprecation/removal
 discard 285ec42  feat(couchjs): add support for SpiderMonkey 86
     add 1042374  feat(couchjs): add support for SpiderMonkey 86
     add 8eb0151  feat: work around get_stacktrace deprecation/removal
     add ce469d9  feat: update deps to support otp23 in a full build
     add 81e6e28  feat: somewhat hacky version detection
     add 9d1a5fc  chore: update dependency pointers to release tags
     add 5ff5fea  chore: simplify version detection h/t @vatamane

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   (7cd3f9b)
            \
             N -- N -- N   refs/heads/feat/3.x/otp23 (5ff5fea)

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:

Reply via email to