This is an automated email from the ASF dual-hosted git repository.
arosien pushed a change to branch update/log4cats-slf4j-2.4.0
in repository https://gitbox.apache.org/repos/asf/daffodil-vscode.git
omit 304065f Merge remote-tracking branch 'upstream/main' into
update/log4cats-slf4j-2.4.0
omit 3d2dc9c Update log4cats-slf4j to 2.4.0
omit 5c38f0c Add debug option that uses configuration from last debug
omit f6713ed Update sbt to 1.7.1
omit 2d6ad05 Bump actions/setup-java from 3.4.0 to 3.4.1
omit 448d288 Multiple Updates:
omit 58dc162 Merge branch 'main' into update/log4cats-slf4j-2.4.0
omit e21d3f5 Update scala dependencies:
omit 084567f Update fs2-io to 3.2.10
omit d4877e2 Update log4cats-slf4j to 2.4.0
add 4480fc4 # This is a combination of 2 commits. # This is the 1st
commit message:
add 80795dc Update log4cats-slf4j to 2.4.0
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 (304065f)
\
N -- N -- N refs/heads/update/log4cats-slf4j-2.4.0 (80795dc)
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:
