From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, for-next, updated. v3.19-rc1-6-gefdca7a
Date: Tue, 23 Dec 2014 22:07:03 -0600 (CST) [thread overview]
Message-ID: <20141224040704.035F67F6C@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
efdca7a Merge branch 'xfs-misc-fixes-for-3.20-1' into for-next
1a43ec0 xfs: Keep sb_bad_features2 consistent with sb_features2
77af574 xfs: remove extra newlines from xfs messages
96ab795 xfs: initialize log buf I/O completion wq on log alloc
d31a182 xfs: Add support to RENAME_EXCHANGE flag
dbe1b5c xfs: Make xfs_vn_rename compliant with renameat2() syscall
from 97bf6af1f928216fd6c5a66e8a57bfa95a659672 (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 efdca7aa3c41bce7a092019b3f675fbaa3b8d23f
Merge: d31a182 1a43ec0
Author: Dave Chinner <david@fromorbit.com>
Date: Wed Dec 24 09:49:53 2014 +1100
Merge branch 'xfs-misc-fixes-for-3.20-1' into for-next
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/libxfs/xfs_format.h | 10 ++--
fs/xfs/xfs_buf_item.c | 2 +-
fs/xfs/xfs_inode.c | 134 ++++++++++++++++++++++++++++++++++++++++++++-
fs/xfs/xfs_inode.h | 2 +-
fs/xfs/xfs_iops.c | 21 +++++--
fs/xfs/xfs_log.c | 10 ++--
fs/xfs/xfs_mount.c | 5 +-
fs/xfs/xfs_super.c | 2 +-
8 files changed, 163 insertions(+), 23 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-24 4:07 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=20141224040704.035F67F6C@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.