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 1cbbea1f2df0 Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux [...] omits 40fd67228d63 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] omits 15705b8d7d32 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new dbee298cb7bb fuse: fix fuse_fill_write_pages() upper bound calculation new 8a6ad7745e13 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new 66c96f160b15 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] new 0748e553df02 userns and mnt_idmap leak in open_tree_attr(2) new 73fa4732d888 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 (1cbbea1f2df0) \ N -- N -- N refs/heads/fs-current (73fa4732d888)
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 5 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: fs/fuse/file.c | 5 ++--- fs/namespace.c | 10 +++------- 2 files changed, 5 insertions(+), 10 deletions(-)