This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a change to branch remove-max-id-purge-limit
in repository https://gitbox.apache.org/repos/asf/couchdb.git
discard d6e9d412b Remove purge max_document_id_number and change
max_revisions_number
add 3f11cfd90 Docs: Update the /_up endpoint docs to include status
response's
add 20e281147 Remove purge max_document_id_number and change
max_revisions_number
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 (d6e9d412b)
\
N -- N -- N refs/heads/remove-max-id-purge-limit (20e281147)
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/docs/src/api/server/common.rst | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
