From: Eryu Guan <eguan@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, Dave Chinner <dchinner@redhat.com>
Subject: Re: [GIT PULL] fstests: updates on 2016-07-31
Date: Wed, 3 Aug 2016 11:20:22 +0800 [thread overview]
Message-ID: <20160803032022.GC27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160802230350.GN12670@dastard>
On Wed, Aug 03, 2016 at 09:03:50AM +1000, Dave Chinner wrote:
> On Sun, Jul 31, 2016 at 10:56:24AM +0800, Eryu Guan wrote:
> > Hi Dave,
> >
> > Can you please pull the fstests update from the location below? This is a small
> > update that only contains some new tests.
>
> Hi Eryu,
>
> I probably won't get to this before friday (merge window stuff
> taking all my time) so if you could update as usual on friday I'll
> pull it all early next week.
Sure. Thanks for the heads up.
Thanks,
Eryu
prev parent reply other threads:[~2016-08-03 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 2:56 [GIT PULL] fstests: updates on 2016-07-31 Eryu Guan
2016-08-02 23:03 ` Dave Chinner
2016-08-03 3:20 ` Eryu Guan [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=20160803032022.GC27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=fstests@vger.kernel.org \
/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