From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-v3.14-rc1-2-12968-ga6cf33b
Date: Thu, 3 Apr 2014 16:16:41 -0500 (CDT) [thread overview]
Message-ID: <20140403211643.00BE629DF9@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
a6cf33b Merge branch 'xfs-bug-fixes-for-3.15-3' into for-next
c88547a xfs: fix directory hash ordering bug
805eeb8 xfs: extra semi-colon breaks a condition
from fe986f9d88ab8079c91669b7f175081f15491a80 (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 a6cf33bc566c5fe888bfa9cf6448037c90661f67
Merge: fe986f9 c88547a
Author: Dave Chinner <david@fromorbit.com>
Date: Fri Apr 4 08:07:35 2014 +1100
Merge branch 'xfs-bug-fixes-for-3.15-3' into for-next
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/xfs_aops.c | 4 ++--
fs/xfs/xfs_da_btree.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
hooks/post-receive
--
XFS development tree
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-04-03 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:16 xfs [this message]
2014-04-03 21:23 ` [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-v3.14-rc1-2-12968-ga6cf33b Dave Chinner
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=20140403211643.00BE629DF9@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