All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/oath-toolkit: bump version to 2.6.13
Date: Fri, 2 Jan 2026 21:56:12 +0100	[thread overview]
Message-ID: <20260102215612.6747b549@windsurf> (raw)
In-Reply-To: <20251223194547.293956-1-ju.o@free.fr>

On Tue, 23 Dec 2025 20:45:47 +0100
Julien Olivain via buildroot <buildroot@buildroot.org> wrote:

> For release announce, see:
> https://mail.gnu.org/archive/html/oath-toolkit-help/2025-07/msg00000.html
> 
> The COPYING license file had minor updates in [1] and other license
> files were removed from the source archive. This commit refect those
> changes.
> 
> [1] https://codeberg.org/oath-toolkit/oath-toolkit/commit/e0fcb3b73d788f0cafdaff0a069e8273d9987777
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Patch tested in:
> https://gitlab.com/jolivain/buildroot/-/pipelines/2230445114
> ---
>  package/oath-toolkit/oath-toolkit.hash | 13 +++++--------
>  package/oath-toolkit/oath-toolkit.mk   |  8 ++------
>  2 files changed, 7 insertions(+), 14 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-01-02 20:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23 19:45 [Buildroot] [PATCH 1/1] package/oath-toolkit: bump version to 2.6.13 Julien Olivain via buildroot
2026-01-02 20:56 ` Thomas Petazzoni via buildroot [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=20260102215612.6747b549@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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.