From: xuyang <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] Oldest still supported kernel
Date: Thu, 16 May 2019 19:09:42 +0800 [thread overview]
Message-ID: <5CDD44F6.6090700@cn.fujitsu.com> (raw)
In-Reply-To: <CAEemH2dj3Txm=otnF+UEg2eJY70wTC-5tbT2R1VfrB0qAxtqmQ@mail.gmail.com>
Hi
>
> On Thu, May 16, 2019 at 5:07 PM Cyril Hrubis <chrubis@suse.cz
> <mailto:chrubis@suse.cz>> wrote:
>
> Hi!
> > > Is it the oldest version we want to support or even something
> older?
> >
> > I'd like minimum to be at least 3.10.0 / glibc-2.17 (RHEL7).
>
>
> This minimum looks good to me.
>
> >
> > Older distros use LTP mostly for regression tests, so it might
> be acceptable
> > for users to switch to older release tag, rather than always
> latest master.
>
>
> I think so. To switch to older release is a better option in that
> situation.
>
> >
> > There's also an option, we create a "legacy" branch for old distros,
> > and accept only critical fixes (no new tests, rewrites, etc.).
> It would
> > be unsupported, but provide place where legacy users can cooperate.
>
> I was trying to avoid having several active branches for LTP for
> several
> reasons. Mainly to avoid people running old LTP on reasonably modern
> kernels because they were under an impression that older release
> is more
> stable. Hence I would like to avoid having this if possible.
>
>
> Yes, to maintain an old LTP branch will also cost more energy, I agree
> to avoid do that too.
>
> But one more question, if a person posts a patch to fix an older issue
> which conflicts with the new kernel stuff, what should we do for that?
In this situation, I think new kernel stuff has a higher priority if
older issue is not very serious.
For Oldest supported , I don't think we must specify a kernel or glibc
oldest version.
Kind Regards
Yang Xu
>
> --
> Regards,
> Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20190516/8fda3284/attachment.html>
next prev parent reply other threads:[~2019-05-16 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 7:38 [LTP] Oldest still supported kernel Petr Vorel
2019-05-16 8:35 ` Jan Stancek
2019-05-16 9:07 ` Cyril Hrubis
2019-05-16 9:49 ` Li Wang
2019-05-16 11:09 ` xuyang [this message]
2019-05-16 12:28 ` Cyril Hrubis
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=5CDD44F6.6090700@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.