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 362a8eb6ec1c Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux [...] omits 98354db229f3 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] adds f90877dd7fb5 seccomp: Stub for !CONFIG_SECCOMP new 619f0b6fad52 Merge tag 'seccomp-v6.13-rc8' of git://git.kernel.org/pub/ [...] new 1ab65b7aec72 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] new 69463ffef658 Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux [...]
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 (362a8eb6ec1c) \ N -- N -- N refs/heads/fs-current (69463ffef658)
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 3 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: include/linux/seccomp.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)