git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Peter Oliver <p.d.oliver@mavit.org.uk>
Cc: git@vger.kernel.org, Peter Oliver <git@mavit.org.uk>
Subject: Re: [PATCH 1/2] Check for Perl 5.26.0 from Meson build
Date: Tue, 21 Jan 2025 07:44:24 +0100	[thread overview]
Message-ID: <Z49CQaW9n86Uml_l@pks.im> (raw)
In-Reply-To: <20250120160301.121245-1-git@mavit.org.uk>

On Mon, Jan 20, 2025 at 04:03:00PM +0000, Peter Oliver wrote:
> Commit 702d8c1 (which landed not long before Meson was added) dropped
> support for Perl versions back to 5.8.1.

Makes sense. This commit was another thing that landed in parallel to
the Meson effort, so it's not surprising that Meson still requires the
old version.

A couple remarks for the commit message:

  - The subject should typically start with the subsystem you're
    touching, followed by a short description of what you're doing to
    it.

  - We aim to make the commit message work standalone, wihtout reading
    the commit subject. So saying something along the lines that the
    minimum required version in MEson hasn't been bumped accordingly
    would make sense.

  - We use `git log -1 --format=reference` when mentioning commits.

So, my suggestion:

    meson: bump minimum required Perl version to 5.26.0

    Commit 702d8c1f3b (Require Perl 5.26.0, 2024-10-23) dropped support
    for Perl versions older than 5.28.0. The Meson build system, which
    has been developed in parallel to that commit, hasn't been bumped
    accordingly and thus still requires Perl 5.8.1 or newer.

    Fix this and require Perl 5.28.0 or newer in Meson, as well.

Patrick

  parent reply	other threads:[~2025-01-21  6:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 16:03 [PATCH 1/2] Check for Perl 5.26.0 from Meson build Peter Oliver
2025-01-20 16:03 ` [PATCH 2/2] Fix Meson Perl version check Peter Oliver
2025-01-21  6:44   ` Patrick Steinhardt
2025-01-21  6:44 ` Patrick Steinhardt [this message]
2025-01-24 16:30 ` [PATCH v2 0/2] " Peter Oliver
2025-01-24 16:30   ` [PATCH v2 1/2] meson: bump minimum required Perl version to 5.26.0 Peter Oliver
2025-01-24 16:30   ` [PATCH v2 2/2] meson: fix Perl version check for Meson versions before 1.7.0 Peter Oliver
2025-01-27  7:39     ` Patrick Steinhardt
2025-02-18 15:30       ` [PATCH v3 0/2] Fix Meson Perl version check Peter Oliver
2025-02-18 15:30         ` [PATCH v3 1/2] meson: bump minimum required Perl version to 5.26.0 Peter Oliver
2025-02-18 15:30         ` [PATCH v3 2/2] meson: fix Perl version check for Meson versions before 1.7.0 Peter Oliver
2025-02-18 19:12         ` [PATCH v3 0/2] Fix Meson Perl version check Junio C Hamano
2025-02-19  7:17           ` Patrick Steinhardt
2025-02-19 16:05             ` Junio C Hamano
2025-02-25 12:28           ` Peter Oliver
2025-02-25 18:20             ` Junio C Hamano

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=Z49CQaW9n86Uml_l@pks.im \
    --to=ps@pks.im \
    --cc=git@mavit.org.uk \
    --cc=git@vger.kernel.org \
    --cc=p.d.oliver@mavit.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).