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

FreeAndNil pushed a change to branch Feature/305-dotnet-10-build-cleanup
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git


    omit 6dee6356 Remove the Mono guards from the tests (#305)
    omit 2924e872 Run CI on the latest runner images (#305)
    omit dc1b0928 Update BUILDING.md to match the actual build
    omit 9c9fb168 Quieten the TelnetAppender test
    omit c3da47c3 Fix the log4net.Ext.Mail package readme
    omit d7912e49 Stop the release scripts on failed steps
    omit 88e881d4 Build the container image from the .NET 10 SDK image
    omit 915c0342 Build net4x without Mono
    omit 69622d9b Target .NET 10 / C# 14 for tests
     add c9e278b2 Target .NET 10 / C# 14 for tests
     add 7f63f490 Build net4x without Mono
     add 27216417 Build the container image from the .NET 10 SDK image
     add 96123c99 Stop the release scripts on failed steps
     add 9fab1adb Fix the log4net.Ext.Mail package readme
     add d3984901 Quieten the TelnetAppender test
     add a73070c5 Update BUILDING.md to match the actual build
     add cfeb2e5d Run CI on the latest runner images (#305)
     add 98742f23 Remove the Mono guards from the tests (#305)

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   (6dee6356)
            \
             N -- N -- N   refs/heads/Feature/305-dotnet-10-build-cleanup 
(98742f23)

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