All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@aperture.us>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/fuse-overlayfs: bump version to 1.11
Date: Sat, 6 May 2023 18:11:05 +0200	[thread overview]
Message-ID: <20230506161105.GS252090@scaer> (raw)
In-Reply-To: <20230504071546.3435096-1-christian@aperture.us>

Christian, All,

On 2023-05-04 00:15 -0700, Christian Stewart via buildroot spake thusly:
> https://github.com/containers/fuse-overlayfs/releases/tag/v1.11
> 
> Signed-off-by: Christian Stewart <christian@aperture.us>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
> 
> v1 -> v2:
> 
>  - fix filename mistake in hash file
> 
> Signed-off-by: Christian Stewart <christian@aperture.us>
> ---
>  package/fuse-overlayfs/fuse-overlayfs.hash | 2 +-
>  package/fuse-overlayfs/fuse-overlayfs.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/fuse-overlayfs/fuse-overlayfs.hash b/package/fuse-overlayfs/fuse-overlayfs.hash
> index aa5438755e..0386687e6f 100644
> --- a/package/fuse-overlayfs/fuse-overlayfs.hash
> +++ b/package/fuse-overlayfs/fuse-overlayfs.hash
> @@ -1,4 +1,4 @@
>  # Locally computed
> -sha256  4351eaed7cf26a5012c14c6e0fc883ef65a7b5dcc95ba129ce485904106c25a9  fuse-overlayfs-1.10.tar.gz
> +sha256  d5558cd419c8d46bdc958064cb97f963d1ea793866414c025906ec15033512ed  fuse-overlayfs-1.11.tar.gz
>  # Locally computed
>  sha256  8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903  COPYING
> diff --git a/package/fuse-overlayfs/fuse-overlayfs.mk b/package/fuse-overlayfs/fuse-overlayfs.mk
> index 1633d3bd41..4db2ccd7d5 100644
> --- a/package/fuse-overlayfs/fuse-overlayfs.mk
> +++ b/package/fuse-overlayfs/fuse-overlayfs.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -FUSE_OVERLAYFS_VERSION = 1.10
> +FUSE_OVERLAYFS_VERSION = 1.11
>  FUSE_OVERLAYFS_SITE = $(call github,containers,fuse-overlayfs,v$(FUSE_OVERLAYFS_VERSION))
>  FUSE_OVERLAYFS_LICENSE = GPL-3.0
>  FUSE_OVERLAYFS_LICENSE_FILES = COPYING
> -- 
> 2.40.1
> 
> _______________________________________________
> 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

      reply	other threads:[~2023-05-06 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  7:15 [Buildroot] [PATCH v2 1/1] package/fuse-overlayfs: bump version to 1.11 Christian Stewart via buildroot
2023-05-06 16:11 ` 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=20230506161105.GS252090@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --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.