<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi<br>
<blockquote
cite="mid:CAEemH2dj3Txm=otnF+UEg2eJY70wTC-5tbT2R1VfrB0qAxtqmQ@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, May 16, 2019 at 5:07
PM Cyril Hrubis <<a moz-do-not-send="true"
href="mailto:chrubis@suse.cz">chrubis@suse.cz</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">Hi!<br>
> > Is it the oldest version we want to support or
even something older?<br>
> <br>
> I'd like minimum to be at least 3.10.0 / glibc-2.17
(RHEL7).<br>
</blockquote>
<div><br>
</div>
<div>
<div class="gmail_default" style="font-size: small;">This
minimum looks good to me.</div>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
> <br>
> Older distros use LTP mostly for regression tests, so
it might be acceptable<br>
> for users to switch to older release tag, rather than
always latest master.<br>
</blockquote>
<div><br>
</div>
<div class="gmail_default" style="font-size: small;">I think
so. To switch to older release is a better option in that
situation.</div>
<div class="gmail_default" style="font-size: small;"></div>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
> <br>
> There's also an option, we create a "legacy" branch for
old distros,<br>
> and accept only critical fixes (no new tests, rewrites,
etc.). It would<br>
> be unsupported, but provide place where legacy users
can cooperate.<br>
<br>
I was trying to avoid having several active branches for LTP
for several<br>
reasons. Mainly to avoid people running old LTP on
reasonably modern<br>
kernels because they were under an impression that older
release is more<br>
stable. Hence I would like to avoid having this if possible.<br>
</blockquote>
<div><br>
</div>
<div>
<div class="gmail_default" style="font-size: small;">Yes, to
maintain an old LTP branch will also cost more energy, I
agree to avoid do that too.</div>
<br>
</div>
<div>
<div class="gmail_default" style="font-size: small;">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? </div>
</div>
</div>
</div>
</blockquote>
In this <span class="gt-baf-term-text"><span class="gt-baf-cell
gt-baf-word-clickable">situation, I think new kernel stuff has
a higher priority if older issue is not very serious.<br>
For Oldest supported , I don't think we must specify a kernel
or glibc oldest version. <br>
</span></span>
<pre wrap=""> Kind Regards
Yang Xu </pre>
<span class="gt-baf-term-text"><span class="gt-baf-cell
gt-baf-word-clickable"></span></span>
<blockquote
cite="mid:CAEemH2dj3Txm=otnF+UEg2eJY70wTC-5tbT2R1VfrB0qAxtqmQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>Regards,<br>
</div>
<div>Li Wang<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>