This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a change to branch shard-split
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
discard f9f6f3b Implement resharding HTTP API
discard 2cb9bd5 Update internal replicator to replicate to multiple targets
discard a075900 Implement initial shard splitting data copy
discard 541aeca Shard splitting job implementation
discard 68d0745 Resharding supervisor and job manager
discard 61d6b75 Uneven shard copy handling in mem3 and fabric
new ca74d12 Update folsom to support newer erlang
new c90c453 Merge pull request #1938 from cloudant/update-folsom
new efc41cd Uneven shard copy handling in mem3 and fabric
new b382139 Resharding supervisor and job manager
new 1d7a7d3 Shard splitting job implementation
new 3d94cf2 Implement initial shard splitting data copy
new 964946e Update internal replicator to replicate to multiple targets
new 44a19f2 Implement resharding HTTP API
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 (f9f6f3b)
\
N -- N -- N refs/heads/shard-split (44a19f2)
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.
The 11617 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
rebar.config.script | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
