This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a change to branch backport-discard
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
discard 363383fd8f Backported more discard() steps from 4.x
discard 545b0ca623 Backported e8b9532fc0ec811460e97ebf5e00b8b9ec9192ac from 4.x
discard 84a63415ee Backported 62a3935152354eea54f2cfadc39edf10ebe2005d from
4.x
new 39ee87903a Backported 62a3935152354eea54f2cfadc39edf10ebe2005d from
4.x
new feba8de6ca Backported e8b9532fc0ec811460e97ebf5e00b8b9ec9192ac from 4.x
new b7d29c83d1 Backported more discard() steps from 4.x
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 (363383fd8f)
\
N -- N -- N refs/heads/backport-discard (b7d29c83d1)
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 3 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:
docs/src/upgrade/release-3.3.x.asciidoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
