From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] September release
Date: Wed, 26 Sep 2018 12:03:38 +0200 [thread overview]
Message-ID: <20180926100338.GA9332@rei> (raw)
In-Reply-To: <CAEemH2dRuE9g9iqyGo+nznqi_fmE17VqYGTj5OvHUxw_FnAFmQ@mail.gmail.com>
Hi!
> > Are there any fixes that should go in before the release is finalized?
> >
>
> What about merging Richard's fzsync API in LTP new release? Is the time
> ample?
I would like to give it a proper review and stabilization period. I
given up on having it included because the patchset is quite complex and
came shortly before we started to work on the release.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2018-09-26 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 8:56 [LTP] September release Cyril Hrubis
2018-09-26 9:59 ` Li Wang
2018-09-26 10:03 ` Cyril Hrubis [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=20180926100338.GA9332@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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