This is an automated email from the ASF dual-hosted git repository.
arm pushed a change to branch safe_paths
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
discard b2261127 #964 - implement constrained safe path type for containment
guarantees
discard 0e795273 Initial safe path work
add f34f4a0a Update to MFA-supporting OAuth endpoints
new ccd37b0a Initial safe path work
new e96cc590 #964 - implement constrained safe path type for containment
guarantees
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 (b2261127)
\
N -- N -- N refs/heads/safe_paths (e96cc590)
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 2 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:
atr/server.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
