From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs: master branch updated to c5d584c
Date: Wed, 11 May 2016 15:00:13 +1000 [thread overview]
Message-ID: <20160511050013.GX18496@dastard> (raw)
In-Reply-To: <20160511002607.GK26977@dastard>
On Wed, May 11, 2016 at 10:26:07AM +1000, Dave Chinner wrote:
> Hi Folks,
>
> The xfsprogs repository at:
>
> git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
>
> has just been updated. Note that this includes the change of mkfs
> command line parsing, so you will see some additional xfstests
> failures resulting from that. Those should be fixed soon as filters
> and changes are made to xfstests to handle these differences.
FYI: I just updated the for-next branch to point at the same commit
as I forgot to do that. The for-next branch rebased in doing this,
so don't be suprised if it won't fast forward...
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:[~2016-05-11 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 0:26 [ANNOUNCE] xfsprogs: master branch updated to c5d584c Dave Chinner
2016-05-11 5:00 ` 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=20160511050013.GX18496@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