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 5aac18af5efc Merge branch 'fixes' of https://git.kernel.org/pub/scm/lin [...] omits f695cd1c1f23 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] new ac3fd01e4c1e Linux 6.18-rc7 new 99f5e611e1c3 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] new 8b227add5248 Merge branch 'fixes' of https://git.kernel.org/pub/scm/lin [...]
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 (5aac18af5efc) \ N -- N -- N refs/heads/fs-current (8b227add5248)
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: Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)