From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
fstests@vger.kernel.org
Subject: Re: e2fsprogs, xfstests git trees pushed
Date: Wed, 17 Dec 2014 07:53:19 +1100 [thread overview]
Message-ID: <20141216205319.GW24183@dastard> (raw)
In-Reply-To: <20141215193139.GA14298@thunk.org>
[cc fstests@vger.kernel.org]
On Mon, Dec 15, 2014 at 02:31:39PM -0500, Theodore Ts'o wrote:
> Per our concall today, I've pushed out an updated version of e2fsprogs
> to git.kernel.org. Darrick, feel free to go ahead and rebase your
> patchbomb against the next branch.
>
> Also, I've pushed out to github
> (https://github.com/tytso/xfstests.git) what I plan to be using for
> testing ext4 for this development cycle. It has the latest changes
> which Dave Chinner pushed out to git.kernel.org, plus three commits
> which have all been sent to the mailing list for review:
>
> Eryu Guan (1):
> generic/299: various fixes
>
> Theodore Ts'o (2):
> common: use mke2fs -F instead of piping in yes
> ext4/308,generic/324: require fallocate support
And now pushed upstream, so your tree needs rebasing again.
Perhaps it would be better for kvm-xfstests to follow the upstream
tree directly and work out some method of tagging the upstream tree
that gives you a defined "release point" for your image builds.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-12-16 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 19:31 e2fsprogs, xfstests git trees pushed Theodore Ts'o
2014-12-16 20:53 ` Dave Chinner [this message]
2014-12-17 3:34 ` Theodore Ts'o
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=20141216205319.GW24183@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).