This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch fs-current in repository linux-next.
omits a3bcaabed7c3 Merge branch 'nfsd-fixes' of git://git.kernel.org/pub/scm/ [...] omits e5fee9362e88 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] omits e8bfa8e9b061 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new 819837584309 Linux 6.12-rc5 new 812e39f7c54a Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new 02519cad3f17 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] new db05f7b3e9d8 Merge branch 'nfsd-fixes' of git://git.kernel.org/pub/scm/ [...]
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 (a3bcaabed7c3) \ N -- N -- N refs/heads/fs-current (db05f7b3e9d8)
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 4 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: Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)