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

dill0wn pushed a change to branch dw/8455
in repository https://gitbox.apache.org/repos/asf/allura.git


 discard 52939214b fixup! fixup! fixup! fixup! [#8455] allura pytest - fix misc 
test failures that popped up during pytest conversion
 discard a2aaab866 fixup! fixup! fixup! [#8455] allura pytest - fix misc test 
failures that popped up during pytest conversion
 discard 8effcc6bd fixup! fixup! [#8455] allura pytest - fix misc test failures 
that popped up during pytest conversion
 discard 47ec7df62 fixup! [#8455] allura pytest - fix misc test failures that 
popped up during pytest conversion
 discard 132365a7e [#8455] allura pytest - fix misc test failures that popped 
up during pytest conversion
 discard 422a25a2e fixup! all trivial failures resolved for ./Allura, only 
legit failures remain
 discard ba1a294cb all trivial failures resolved for ./Allura, only legit 
failures remain
 discard 8500cccc7 All tests in ./Allura collecting, and test_auth completely 
passing
 discard c5ee77989 first substantial test file mostly passing under pytest
 discard a784125bf 8455 nose2pytest for ./Allura
     add 69eb40e26 [#8460] add new smtpclient method send_raw which sends 
pre-formatted email content
     add df9b6a2bc [#8462] Redirect any missing tools as 301 instead of 404
     add 143711e43 [#8462] minor test fix
     add 3da11b88b fix sphinx documentation issues
     add 282210452 bump ming to latest version
     new 41e6ada26 8455 nose2pytest for ./Allura
     new 6cb9308bd first substantial test file mostly passing under pytest
     new d247108c0 All tests in ./Allura collecting, and test_auth completely 
passing
     new 822573fb1 all trivial failures resolved for ./Allura, only legit 
failures remain
     new 32da7de20 [#8455] allura pytest - fix misc test failures that popped 
up during pytest conversion

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   (52939214b)
            \
             N -- N -- N   refs/heads/dw/8455 (32da7de20)

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 5 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:
 Allura/allura/command/show_models.py                    |  3 ++-
 Allura/allura/controllers/project.py                    | 12 ++++++++----
 Allura/allura/lib/mail_util.py                          |  8 ++++++--
 Allura/allura/lib/plugin.py                             |  3 +--
 Allura/allura/model/artifact.py                         |  2 +-
 Allura/allura/tests/functional/test_neighborhood.py     |  4 ++--
 Allura/docs/api/lib/security.rst                        |  1 +
 Allura/docs/getting_started/install_each_step.rst       |  5 ++---
 ForgeImporters/forgeimporters/base.py                   |  2 +-
 ForgeTracker/forgetracker/tests/functional/test_root.py |  2 +-
 requirements.txt                                        |  2 +-
 11 files changed, 26 insertions(+), 18 deletions(-)

Reply via email to