From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: haproxy: update to 2.6.9.
Date: Tue, 14 Feb 2023 18:44:25 +0100 [thread overview]
Message-ID: <20230214174425.n_Xt7HvTBoEg4-gnDW-fo0zdmHaUxMZ6GcwOEGDlI2U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42194@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
There's a merged pull request on the void-packages repository
haproxy: update to 2.6.9.
https://github.com/void-linux/void-packages/pull/42194
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
HAProxy 2.6 is the latest LTS release with some nice improvements over the 2.4 series. Until another LTS hits, it's reasonable to lock the package to 2.6.x.
prev parent reply other threads:[~2023-02-14 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:29 [PR PATCH] haproxy: update to 2.6.8 zdykstra
2023-02-10 22:40 ` [PR REVIEW] " paper42
2023-02-10 22:40 ` paper42
2023-02-10 22:49 ` zdykstra
2023-02-10 22:49 ` [PR PATCH] [Updated] " zdykstra
2023-02-10 22:50 ` [PR REVIEW] " zdykstra
2023-02-10 23:22 ` [PR PATCH] [Updated] " zdykstra
2023-02-10 23:23 ` zdykstra
2023-02-14 16:30 ` [PR PATCH] [Updated] " zdykstra
2023-02-14 16:30 ` zdykstra
2023-02-14 16:33 ` [PR PATCH] [Updated] haproxy: update to 2.6.9 zdykstra
2023-02-14 17:40 ` zdykstra
2023-02-14 17:44 ` classabbyamp [this message]
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=20230214174425.n_Xt7HvTBoEg4-gnDW-fo0zdmHaUxMZ6GcwOEGDlI2U@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 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).