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.12-11704-g46f23ad
Date: Fri, 13 Dec 2013 14:22:11 -0600 (CST)	[thread overview]
Message-ID: <20131213202213.3A4057F53@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
  46f23ad Merge branch 'xfs-factor-icluster-macros' into for-next
  f9e5abc xfs: use xfs_icluster_size_fsb in xfs_imap
  982e939 xfs: use xfs_icluster_size_fsb in xfs_ifree_cluster
  6e0c7b8 xfs: use xfs_icluster_size_fsb in xfs_ialloc_inode_init
  a2ba07b xfs: use xfs_icluster_size_fsb in xfs_bulkstat
  904957b xfs: introduce a common helper xfs_icluster_size_fsb
  126cd10 xfs: get rid of XFS_IALLOC_BLOCKS macros
  0f49efd xfs: get rid of XFS_INODE_CLUSTER_SIZE macros
  7178343 xfs: get rid of XFS_IALLOC_INODES macros
  ffda4e8 xfs: remove the quotaoff log format from the quotaoff log item
  ce8e962 xfs: remove the dquot log format from the dquot log item
  2f25129 xfs: remove the inode log format from the inode log item
  da77650 xfs: format logged extents directly into the CIL
  bde7cff xfs: format log items write directly into the linear CIL buffer
  1234351 xfs: introduce xlog_copy_iovec
  3de559f xfs: refactor xfs_inode_item_format
  ce9641d xfs: refactor xfs_inode_item_size
  7aeb722 xfs: refactor xfs_buf_item_format_segment
  9597df6 xfs: remove duplicate code in xlog_cil_insert_format_items
      from  f9b395a8ef8f34d19cae2cde361e19c96e097fad (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 46f23adf78545c49591619a615edeec41ed5a549
Merge: ffda4e8 f9e5abc
Author: Ben Myers <bpm@sgi.com>
Date:   Fri Dec 13 14:15:33 2013 -0600

    Merge branch 'xfs-factor-icluster-macros' into for-next

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

Summary of changes:
 fs/xfs/xfs_buf_item.c     | 103 ++++++------
 fs/xfs/xfs_dquot_item.c   |  67 +++-----
 fs/xfs/xfs_dquot_item.h   |   3 +-
 fs/xfs/xfs_extfree_item.c |  21 +--
 fs/xfs/xfs_ialloc.c       |  53 +++---
 fs/xfs/xfs_ialloc.h       |  21 +--
 fs/xfs/xfs_icreate_item.c |  10 +-
 fs/xfs/xfs_inode.c        |  23 +--
 fs/xfs/xfs_inode_fork.c   |  15 +-
 fs/xfs/xfs_inode_item.c   | 400 +++++++++++++++++++---------------------------
 fs/xfs/xfs_inode_item.h   |   5 -
 fs/xfs/xfs_itable.c       |  22 ++-
 fs/xfs/xfs_log.h          |  46 ++++++
 fs/xfs/xfs_log_cil.c      |  74 +++------
 fs/xfs/xfs_log_recover.c  |  16 +-
 fs/xfs/xfs_trans.h        |   2 +-
 fs/xfs/xfs_trans_resv.c   |  10 +-
 fs/xfs/xfs_trans_space.h  |   2 +-
 18 files changed, 399 insertions(+), 494 deletions(-)


hooks/post-receive
-- 
XFS development tree

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

                 reply	other threads:[~2013-12-13 20:22 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=20131213202213.3A4057F53@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