public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] doc: Add supported kernel, libc versions
Date: Mon, 17 May 2021 08:42:54 +0200	[thread overview]
Message-ID: <YKIQbr8nI0VhFmUg@pevik> (raw)
In-Reply-To: <CAASaF6ytbCjwOSOywR4JUToJb_u9fOe2a2y4zE7_n99cgre5TQ@mail.gmail.com>

Hi,

...
> > Older distributions are not officially supported, which means that it
> > may or may not work. It all depends on your luck. It should be possible
> > to compile latest LTP even on slightly older distributions than we
> > support with a few manual tweaks, e.g. disabling manually tests for
> > newly added syscalls manually, etc.

> > If latest LTP cannot be compiled even with some amount of workarounds,
> > you may result to older LTP releases, however these are _not_ supported
> > in any way. Also if you are trying to run LTP on more than 10 years old
> > distribution you may as well reconsider you life choices.

> Should we also give some hint about accepting patches/wokrarounds for
> very old distros?
> For example: "Trivial fixes/workarounds may be accepted, but users are
> encouraged to move to newer distro."

+1. I'd add it at the end of first paragraph. Or anyone feel free to express it
differently.

Kind regards,
Petr

  reply	other threads:[~2021-05-17  6:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 13:26 [LTP] [RFC PATCH 1/1] doc: Add supported kernel, libc versions Petr Vorel
2021-05-14 13:53 ` Cyril Hrubis
2021-05-14 15:06   ` [LTP] [Automated-testing] " Petr Vorel
2021-05-17 13:56     ` Cyril Hrubis
2021-05-18  8:29       ` Li Wang
2021-05-17  5:55   ` [LTP] " Jan Stancek
2021-05-17  6:42     ` Petr Vorel [this message]
2021-05-17  5:49 ` xuyang2018.jy
2021-05-17  6:50   ` Petr Vorel

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=YKIQbr8nI0VhFmUg@pevik \
    --to=pvorel@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