public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, for-next, updated. v3.18-rc2-28-gc14fc01
Date: Sun, 30 Nov 2014 18:30:44 -0600 (CST)	[thread overview]
Message-ID: <20141201003044.CFC057F5A@oss.sgi.com> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".

The branch, for-next has been updated
  c14fc01 Merge branch 'xfs-coccinelle-cleanups' into for-next
  d254aae xfs: fix simple_return.cocci warning in xfs_bmse_shift_one
  8300475 xfs: fix simple_return.cocci warning in xfs_file_readdir
  b72091f libxfs: fix simple_return.cocci warnings
  d2a5e3c xfs: remove unnecessary null checks
      from  216875a594e0b4fc72830e3690b8fbe7430738e2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c14fc01340dd0afe58d8671acc3ea5e907e707ae
Merge: 216875a d254aae
Author: Dave Chinner <david@fromorbit.com>
Date:   Mon Dec 1 09:03:02 2014 +1100

    Merge branch 'xfs-coccinelle-cleanups' into for-next

-----------------------------------------------------------------------

Summary of changes:
 fs/xfs/libxfs/xfs_bmap.c   |  6 +-----
 fs/xfs/libxfs/xfs_ialloc.c |  6 +-----
 fs/xfs/xfs_file.c          |  6 +-----
 fs/xfs/xfs_qm.c            | 12 +++++-------
 fs/xfs/xfs_super.c         |  3 +--
 5 files changed, 9 insertions(+), 24 deletions(-)


hooks/post-receive
-- 
XFS development tree

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2014-12-01  0:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141201003044.CFC057F5A@oss.sgi.com \
    --to=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox