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 b45bb3a84a8b Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux [...] omits c25548d505c9 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] omits 4d91cc4fc8b7 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new ac1e21bd8c88 jbd2: increase IO priority for writing revoke records new a0851ea9cd55 jbd2: flush filesystem device before updating tail sequence new 930e7c209b77 Merge patch series "jbd2: two straightforward fixes" new 3eee03fb1de1 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new a10f6bd3e5f2 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] new 18a10043b183 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 (b45bb3a84a8b) \ N -- N -- N refs/heads/fs-current (18a10043b183)

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 6 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/jbd2/commit.c | 4 ++-- fs/jbd2/revoke.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)