All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] configure.ac: Require 2.64
Date: Wed, 4 Jan 2023 10:11:14 +0100	[thread overview]
Message-ID: <Y7VCssq333Y5QgPt@pevik> (raw)
In-Reply-To: <CAEemH2c69cKYLFzivuCRNnpxB8sco-9LRhL8_EYw0i+Srp71CA@mail.gmail.com>

Hi Li,

> Hi Petr,

> I see other places also used 2.61, do you think we need to correct them as
> well?
> (e.g. open-posix and realtime)

> $ git grep AC_PREREQ
> configure.ac:AC_PREREQ(2.61)
> testcases/open_posix_testsuite/configure.ac:AC_PREREQ(2.61)
> testcases/realtime/configure.ac:AC_PREREQ(2.61)

Sure, I could do that, but these independent projects actually work with older
version, that's why I didn't do that.

FYI realtime will go away, once I find time to port relevant tests to rt_tests
and openposix could one day become in separate git.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-01-04  9:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 12:45 [LTP] [PATCH 1/2] configure.ac: Require 2.64 Petr Vorel
2023-01-03 12:45 ` [LTP] [PATCH 2/2] configure.ac: Update AC_PROG_AR related comment Petr Vorel
2023-01-10  9:25   ` Richard Palethorpe
2023-01-10 16:14     ` Petr Vorel
2023-01-10 19:03       ` Zack Weinberg
2023-01-10 20:12         ` Petr Vorel
2023-01-12 10:21           ` Richard Palethorpe
2023-01-03 13:30 ` [LTP] [PATCH 1/2] configure.ac: Require 2.64 Petr Vorel
2023-01-04  3:07 ` Li Wang
2023-01-04  9:11   ` Petr Vorel [this message]
2023-01-04  9:37     ` Li Wang
2023-01-10  9:48       ` Richard Palethorpe

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=Y7VCssq333Y5QgPt@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=vapier@gentoo.org \
    /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.