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

mattsicker pushed a change to branch feature/3.x/port-3259
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


    omit 34f0004808 Support `FailoverAppender::requiresLocation`
     add a109d05742 Support `FailoverAppender::requiresLocation`

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   (34f0004808)
            \
             N -- N -- N   refs/heads/feature/3.x/port-3259 (a109d05742)

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:
 .../.3.x.x/3257_fix_FailoverAppender_requiresLocation.xml         | 8 --------
 1 file changed, 8 deletions(-)
 delete mode 100644 
src/changelog/.3.x.x/3257_fix_FailoverAppender_requiresLocation.xml

Reply via email to