From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/prosody: security bump to 0.11.12
Date: Sat, 22 Jan 2022 14:54:36 +0100 [thread overview]
Message-ID: <20220122145436.080cda5b@windsurf> (raw)
In-Reply-To: <20220117113656.234077-1-francois.perrad@gadz.org>
On Mon, 17 Jan 2022 12:36:56 +0100
Francois Perrad <fperrad@gmail.com> wrote:
> see https://blog.prosody.im/prosody-0.11.12-released/
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/prosody/prosody.hash | 8 ++++----
> package/prosody/prosody.mk | 2 +-
> 2 files changed, 5 insertions(+), 5 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
next prev parent reply other threads:[~2022-01-22 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 11:36 [Buildroot] [PATCH] package/prosody: security bump to 0.11.12 Francois Perrad
2022-01-22 13:54 ` Thomas Petazzoni [this message]
2022-01-28 19:33 ` 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=20220122145436.080cda5b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=fperrad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox