This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to annotated tag next-20221226 in repository linux-next.

*** WARNING: tag next-20221226 was modified! ***

from 20122a5b4465 (tag) to fbb3e53b6f5b (tag) tagging c76083fac3bae1a87ae3d005b5cb1cbc761e31d5 (commit) replaces v6.2-rc1 tagged by Stephen Rothwell on Mon Dec 26 12:44:52 2022 +1100

- Log ----------------------------------------------------------------- next-20221226

-----------------------------------------------------------------------

discards a7afbfebf307 Add linux-next specific files for 20221226 new c76083fac3ba Add linux-next specific files for 20221226

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the annotated tag 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 (20122a5b4465) \ N -- N -- N refs/tags/next-20221226 (fbb3e53b6f5b)

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 "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: