From: Peter Korsgaard <peter@korsgaard.com>
To: Yair Ben-Avraham via buildroot <buildroot@buildroot.org>
Cc: Yair Ben-Avraham <yairba@protonmail.com>
Subject: Re: [Buildroot] [PATCH] package/gloox: bump version to 1.0.28
Date: Sat, 09 Dec 2023 16:03:47 +0100 [thread overview]
Message-ID: <87h6krpgdo.fsf@48ers.dk> (raw)
In-Reply-To: <Db9O_yrfPJCilzgeet7a7WTUMEe5k1lE366mkze_f7XgY7RJkKN6rLbxXz_fBNYaTrFFF06yDy8O-49GOs9lLRT6pcCMugsHI-EES3z7Usg=@protonmail.com> (Yair Ben-Avraham via buildroot's message of "Wed, 06 Dec 2023 09:32:47 +0000")
>>>>> "Yair" == Yair Ben-Avraham via buildroot <buildroot@buildroot.org> writes:
> Signed-off-by: Yair Ben-Avraham <yairba@protonmail.com>
> ---
> package/gloox/gloox.hash | 2 +-
> package/gloox/gloox.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> diff --git a/package/gloox/gloox.hash b/package/gloox/gloox.hash
> index 66a3c2d1be..963b798299 100644
> --- a/package/gloox/gloox.hash
> +++ b/package/gloox/gloox.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 0b8b7371439bc58d9e51384b616c964b18b7b41b87af1b7855104380eda86ffb gloox-1.0.27.tar.bz2
> +sha256 591bd12c249ede0b50a1ef6b99ac0de8ef9c1ba4fd2e186f97a740215cc5966c gloox-1.0.28.tar.bz2
> sha256 40a20c41c8dabb8ba61bea983fa8f2f6989e67fac56bb62c2249053807fd26af LICENSE
> diff --git a/package/gloox/gloox.mk b/package/gloox/gloox.mk
Something (your mailer?) ate a bunch of white space, so I had to fix
that up manually. Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-09 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 9:11 [Buildroot] [PATCH] package/gloox: bump version to 1.0.28 Yair Ben-Avraham via buildroot
2023-12-06 9:32 ` Yair Ben-Avraham via buildroot
2023-12-09 15:03 ` Peter Korsgaard [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=87h6krpgdo.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=yairba@protonmail.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