From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RESEND PATCH] package/libostree: bump to version 2023.2
Date: Sat, 6 May 2023 16:43:00 +0200 [thread overview]
Message-ID: <20230506144300.GF2661@scaer> (raw)
In-Reply-To: <20230504073820.16831-1-marcus.folkesson@gmail.com>
Marcus, All,
On 2023-05-04 09:38 +0200, Marcus Folkesson spake thusly:
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
There is no need to resend a patch: we do not lose patches as they are
all tracked in patchwork, and this is where maintainers get the list of
pending patches:
https://patchwork.ozlabs.org/project/buildroot/list/
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/libostree/libostree.hash | 2 +-
> package/libostree/libostree.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/libostree/libostree.hash b/package/libostree/libostree.hash
> index 63dfe98d80..db99b4b07b 100644
> --- a/package/libostree/libostree.hash
> +++ b/package/libostree/libostree.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 dd792b167693a1971c9f6e3168013d906ac035100ff6c719a3b322eb44b96f55 libostree-2023.1.tar.xz
> +sha256 ceb0788755a0bff5738d44543552fbf883cf71df481baa3ca7288da7a402bb85 libostree-2023.2.tar.xz
> sha256 b7993225104d90ddd8024fd838faf300bea5e83d91203eab98e29512acebd69c COPYING
> diff --git a/package/libostree/libostree.mk b/package/libostree/libostree.mk
> index 4b17fcf391..367a833ac9 100644
> --- a/package/libostree/libostree.mk
> +++ b/package/libostree/libostree.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -LIBOSTREE_VERSION = 2023.1
> +LIBOSTREE_VERSION = 2023.2
> LIBOSTREE_SOURCE = libostree-$(LIBOSTREE_VERSION).tar.xz
> LIBOSTREE_SITE = https://github.com/ostreedev/ostree/releases/download/v$(LIBOSTREE_VERSION)
>
> --
> 2.39.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-05-06 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 7:38 [Buildroot] [RESEND PATCH] package/libostree: bump to version 2023.2 Marcus Folkesson
2023-05-06 14:43 ` Yann E. MORIN [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=20230506144300.GF2661@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=marcus.folkesson@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