(logging-log4net) branch master updated: #314 - implemented by -> fixed by

[fr...@apache.org]

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

FreeAndNil pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git


The following commit(s) were added to refs/heads/master by this push:
     new 8e881c60 #314 - implemented by -> fixed by
8e881c60 is described below

commit 8e881c60f076fc55f082fa3c95fc86ef1575ff73
Author: Jan Friedrich <fr...@apache.org>
AuthorDate: Sun Sep 27 21:43:43 2026 +0200

    #314 - implemented by -> fixed by
---
 src/changelog/3.5.0/314-adonet-retry-cap.xml                 | 2 +-
 src/changelog/3.5.0/314-flush-reports-buffered-events.xml    | 2 +-
 src/changelog/3.5.0/314-remote-syslog-background-sender.xml  | 2 +-
 src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/changelog/3.5.0/314-adonet-retry-cap.xml b/src/changelog/3.5.0/314-adonet-retry-cap.xml
index 4a32b49b..fb5ce248 100644
--- a/src/changelog/3.5.0/314-adonet-retry-cap.xml
+++ b/src/changelog/3.5.0/314-adonet-retry-cap.xml
@@ -9,6 +9,6 @@
  written. Retrying after a rolled back transaction was added in 3.4.0 to save the events around
  the one the database rejected, but a batch that fails outright, such as a missing table or a
  missing permission, then cost one round trip per event: 513 instead of 1 for a full buffer. It
- now gives up after five consecutive failures (implemented by @FreeAndNil)
+ now gives up after five consecutive failures (fixed by @FreeAndNil)
   </description>
 </entry>
diff --git a/src/changelog/3.5.0/314-flush-reports-buffered-events.xml b/src/changelog/3.5.0/314-flush-reports-buffered-events.xml
index 535f067d..9a886e3a 100644
--- a/src/changelog/3.5.0/314-flush-reports-buffered-events.xml
+++ b/src/changelog/3.5.0/314-flush-reports-buffered-events.xml
@@ -7,6 +7,6 @@
   <description format="asciidoc">
     report a buffering appender that is still holding events from `Flush`. It returned `true`
  unconditionally, including for a `lossy` appender, where flushing deliberately does nothing and
- every buffered event stays where it was (implemented by @FreeAndNil)
+ every buffered event stays where it was (fixed by @FreeAndNil)
   </description>
 </entry>
diff --git a/src/changelog/3.5.0/314-remote-syslog-background-sender.xml b/src/changelog/3.5.0/314-remote-syslog-background-sender.xml
index 1894ef20..8dbae122 100644
--- a/src/changelog/3.5.0/314-remote-syslog-background-sender.xml
+++ b/src/changelog/3.5.0/314-remote-syslog-background-sender.xml
@@ -9,6 +9,6 @@
  stopped accepting datagrams grew it until the process ran out of memory, and shutdown waited five
  seconds and then abandoned a drain that had no limit of its own. It now holds `sendQueueSize`
  datagrams (500), a logging call waits at most `enqueueTimeoutMillis` (5000) for room, losses are
- counted and reported, and `Flush` honours its timeout (audit da18b6fd-f034, implemented by @FreeAndNil)
+ counted and reported, and `Flush` honours its timeout (audit da18b6fd-f034, fixed by @FreeAndNil)
   </description>
 </entry>
diff --git a/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml b/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml
index 2785a792..e7524f88 100644
--- a/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml
+++ b/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml
@@ -9,6 +9,6 @@
  connection its background pump owns, but also inherited one from `UdpAppender` that nothing ever
  used, which bound `localPort` twice. A pump that cannot connect now reports it as well, instead
  of ending unobserved and leaving every later event queued behind a sender that is gone
- (audit da18b6fd-f034, implemented by @FreeAndNil)
+ (audit da18b6fd-f034, fixed by @FreeAndNil)
   </description>
 </entry>