From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] LTP release && Christmas && New year
Date: Mon, 2 Jan 2017 13:31:42 +0100 [thread overview]
Message-ID: <20170102123142.GD20636@rei.lan> (raw)
In-Reply-To: <20161212132204.GA21779@rei.lan>
Hi!
> I will be on a time off since the next week so I propose to work on
> merging as many patches as possible this week. Then we will follow up
> with pre-release testing and freeze. I will join the effort once I
> return back to the work which will be Monday 2. 1. 2017. then we will do
> the release a week or two after that. Does that sound OK to everyone?
And I'm back. I will try to do something about implicit function
warnings on older distributions introduced by recent addition of
pread(), pwrite() and getpgid() into the safe macros header, then
do a few runs on different distros/hardware.
Is there anything that should be considered for a release?
I guess that we should merge the fix for aarch64 check in max_map_count
test.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-01-02 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 13:22 [LTP] LTP release && Christmas && New year Cyril Hrubis
2016-12-13 9:34 ` Jan Stancek
2017-01-02 12:31 ` Cyril Hrubis [this message]
2017-01-10 1:43 ` Cui Bixuan
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=20170102123142.GD20636@rei.lan \
--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