You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by va...@apache.org on 2020/02/19 23:26:27 UTC
[couchdb] branch fix/single-node-status-3.0.x updated (4f723bb ->
399ba34)
This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a change to branch fix/single-node-status-3.0.x
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
discard 4f723bb fix: show single node on setup status with single_node=true
omit 45f2469 Revert "fix: single node state (#2574)"
add 5f6a76d bump docs rev (#2579)
add a5f7b4f Revert "fix: single node state (#2574)"
add 399ba34 fix: show single node on setup status with single_node=true
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 (4f723bb)
\
N -- N -- N refs/heads/fix/single-node-status-3.0.x (399ba34)
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:
rebar.config.script | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)