From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-v3.14-rc1-2-12968-ga6cf33b
Date: Fri, 4 Apr 2014 08:23:22 +1100 [thread overview]
Message-ID: <20140403212322.GO17603@dastard> (raw)
In-Reply-To: <20140403211643.00BE629DF9@oss.sgi.com>
On Thu, Apr 03, 2014 at 04:16:41PM -0500, xfs@oss.sgi.com wrote:
> 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.
Folks, this is the branch I plan to tag and send to Linus to pull
tomorrow morning. It would be appreciated if people can run eyes
over it and test it before I do that.
FWIW, I plan to get all the other DIO/getblocks data corruption
issues sorted out and send them as a separate pull request (possibly
for -rc2) once they have had further testing.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-04-03 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:16 [XFS updates] XFS development tree branch, for-next, updated. xfs-for-linus-v3.14-rc1-2-12968-ga6cf33b xfs
2014-04-03 21:23 ` Dave Chinner [this message]
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=20140403212322.GO17603@dastard \
--to=david@fromorbit.com \
--cc=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