This is an automated email from the ASF dual-hosted git repository.

sbp pushed a change to branch remove-hardcoded-tooling-users
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git


    omit f04e8711 sets and lists
    omit d4c44183 Remove hardcoded tooling users
     add d7739e3c Adding comment; fixes #773
     add c2e1f7d1 Adding comment; fixes #767
     add 8b22964a Adding a comment about octet-stream; fixes #714
     add 5311b7e4 Adding comment about data display; fixes #711
     add 7bd8eafc #656 - add check_access to remaining handlers
     add 84e9697e Fix JWT token validation
     add 721ec859 Remove hardcoded tooling users
     add 72b89357 sets and lists

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   (f04e8711)
            \
             N -- N -- N   refs/heads/remove-hardcoded-tooling-users (72b89357)

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:
 atr/form.py                 |  1 +
 atr/get/distribution.py     | 12 ++++++++----
 atr/get/download.py         |  6 +++++-
 atr/get/finish.py           |  1 +
 atr/get/ignores.py          |  3 ++-
 atr/get/result.py           |  1 +
 atr/jwtoken.py              |  5 ++++-
 atr/post/distribution.py    |  2 ++
 atr/post/ignores.py         |  1 +
 atr/post/keys.py            |  1 +
 atr/storage/writers/vote.py |  1 +
 11 files changed, 27 insertions(+), 7 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to