From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] LTP release and code freeze
Date: Wed, 27 Sep 2017 15:17:59 +0200 [thread overview]
Message-ID: <20170927131758.GC25847@rei> (raw)
In-Reply-To: <20170919084849.GA14328@rei>
Hi!
Here is a status update for the release:
o the cve patchset will not make it
o I tested the utimensat patch I've done and it seems to work fine
- it would be nice if anybody else could have a look before it gets
commited
o the cpuset should be considered for merge as well
Other than that I do not see any blockers.
I would like to release LTP on Friday once the two outstanding issues
are fixed. Is that OK with everyone?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-09-27 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 8:48 [LTP] LTP release and code freeze Cyril Hrubis
2017-09-19 18:26 ` Sandeep Patil
2017-09-27 13:17 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 7:21 Naresh Kamboju
2017-09-19 8:04 ` Cyril Hrubis
2017-09-25 20:00 ` Naresh Kamboju
2017-09-26 8:51 ` Li Wang
2017-09-26 19:18 ` Naresh Kamboju
2017-09-27 1:52 ` Li Wang
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=20170927131758.GC25847@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