All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Mohammad Sharifat <sharifatm904@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Please bump the WireGuard buildroot package
Date: Sun, 31 May 2026 22:57:52 +0200	[thread overview]
Message-ID: <87bjdve1pr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+sxNS3xTJMWVSEStFTmUfCBQ_QFH62DqoKx9pkQAsga-V5eow@mail.gmail.com> (Mohammad Sharifat's message of "Sun, 31 May 2026 17:06:56 +0330")

>>>>> "Mohammad" == Mohammad Sharifat <sharifatm904@gmail.com> writes:

 > Hey,
 > As a user of your WireGuard buildroot package, I thought I'd let you know
 > that wireguard-tools version 1.0.20260223 has been released. Could you bump
 > your package?

Ehh, this was bumped back in March with:

commit ef12f5bb2c79a533e978cbaaf911b5ba96e97439
Author: Peter Korsgaard <peter@korsgaard.com>
Date:   Fri Mar 20 07:53:29 2026 +0100

    package/wireguard-tools: bump version to 1.0.20260223

    For details, see the announcement:
    https://lists.zx2c4.com/pipermail/wireguard/2026-February/009514.html

    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
    Signed-off-by: Julien Olivain <ju.o@free.fr>

Please use 2026.05-rcX or wait a few days for the final 2026.05 release.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2026-05-31 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+sxNS3xTJMWVSEStFTmUfCBQ_QFH62DqoKx9pkQAsga-V5eow@mail.gmail.com>
2026-05-31 20:57 ` Peter Korsgaard [this message]
     [not found] <CAJO3WigJJMVOKW43ujKRuOQSjnACgnT-7=n7XrVXTy6HyXc+Qw@mail.gmail.com>
2026-07-17 20:17 ` [Buildroot] Please bump the WireGuard buildroot package Peter Korsgaard

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=87bjdve1pr.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=sharifatm904@gmail.com \
    /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.