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 ae46ef7f6721 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] omits d681525fd169 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new 835679f01412 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new eccda439dd3c Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] new f1d673b38cb8 fix proc_sys_compare() handling of in-lookup dentries new 7f5940d47ea6 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 (ae46ef7f6721) \ N -- N -- N refs/heads/fs-current (7f5940d47ea6)
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: fs/proc/proc_sysctl.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-)