You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by ja...@apache.org on 2021/03/15 10:23:55 UTC
[couchdb] branch feat/3.x/otp23 updated (0f8b2a9 -> 95581bb)
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 0f8b2a9 chore: simplify version detection h/t @vatamane
omit 2624a8b chore: update dependency pointers to release tags
omit 70334b3 feat: somewhat hacky version detection
omit 233522c feat: update deps to support otp23 in a full build
omit 6423dcf feat: work around get_stacktrace deprecation/removal
omit 61f3879 feat(couchjs): add support for SpiderMonkey 86
add ae74720 Added override for COUCHDB_FAUXTON_DOCROOT (#3335)
add 285ec42 feat(couchjs): add support for SpiderMonkey 86
add 4d75411 feat: work around get_stacktrace deprecation/removal
add 94766ce feat: update deps to support otp23 in a full build
add de511fb feat: somewhat hacky version detection
add 95b24b8 chore: update dependency pointers to release tags
add 95581bb 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 (0f8b2a9)
\
N -- N -- N refs/heads/feat/3.x/otp23 (95581bb)
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:
rel/files/couchdb.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)