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

potiuk pushed a change to branch python-3-11
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 2b754871de fixup! Use parametrize to avoid if else in tests
 discard 7142b3d612 Use parametrize to avoid if else in tests
 discard 3573c54343 Better looping code in setup.py
 discard 020a171db3 Cosmetic
 discard 334e87289c fixup! fixup! fixup! Attempt to add Python 3.11 support
 discard 02a478f29f fixup! fixup! Attempt to add Python 3.11 support
 discard 4126ee6cfc fixup! Attempt to add Python 3.11 support
 discard 28c7a133da Attempt to add Python 3.11 support
     add d25b1945a6 Fixed a small typo in self-hosted (#31464)
     add e30ef21d16 Attempt to add Python 3.11 support
     add 41bc51cc66 fixup! Attempt to add Python 3.11 support
     add 82e45bedc9 fixup! fixup! Attempt to add Python 3.11 support
     add 68018b4538 fixup! fixup! fixup! Attempt to add Python 3.11 support
     add a3162d2172 Cosmetic
     add 4178cdaf48 Better looping code in setup.py
     add 37ecfe64e9 Use parametrize to avoid if else in tests
     add 9473115f65 fixup! Use parametrize to avoid if else in tests

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   (2b754871de)
            \
             N -- N -- N   refs/heads/python-3-11 (9473115f65)

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:
 .github/workflows/build-images.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to