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

bdemers pushed a change to branch tls-for-its-16x
in repository https://gitbox.apache.org/repos/asf/shiro.git.


 discard 94e17fc  Update AbstractContainerIT to allow for HTTPS connections
 discard f0782f4  Add name to ShiroFilter's @ConditionalOnMissingBean
     add d7d36a6  Merge pull request #253 from bmhm/1.6.x_junit4fix
     add 886569d  Add name to ShiroFilter's @ConditionalOnMissingBean
     add ea680b4  Merge pull request #255 from 
ricardolsmendes/add-name-shirofilter-conditional
     add 216e0bf  Update AbstractContainerIT to allow for HTTPS connections

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   (94e17fc)
            \
             N -- N -- N   refs/heads/tls-for-its-16x (216e0bf)

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:

Reply via email to