All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Julien Olivain <ju.o@free.fr>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nfs-utils: security bump version to 2.8.7
Date: Mon, 16 Mar 2026 00:07:43 +0100	[thread overview]
Message-ID: <20260315230743.GB267706@pevik> (raw)
In-Reply-To: <06e35fabddb8f84102a922b63710ea3d@free.fr>

Hi Julien,

> Hi Giulio,

> On 13/03/2026 22:10, Giulio Benetti wrote:
> > Release announce:
> > https://lore.kernel.org/linux-nfs/4d11b9d7-7b49-4a1e-8c26-29ecb2fefe2f@redhat.com/

> The commit title says it is a "security" bump. I can't find any reference to
> security
> fixes in the release note. Could you provide details?

> Or is it a copy paste error from the previous bump?
> https://gitlab.com/buildroot.org/buildroot/-/commit/7dfd2feb445c2cf83a2b52057fab96e72e42a071

> In the later case, no need to send a v2, I'll just remove "security" while
> applying.

I'd also say it's just a copy paste from 2.8.6. 2.8.7 seems to me only a bugfix
release.

Kind regards,
Petr

> > Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>

> Best regards,

> Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-03-15 23:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 21:10 [Buildroot] [PATCH] package/nfs-utils: security bump version to 2.8.7 Giulio Benetti
2026-03-14 19:57 ` Petr Vorel
2026-03-15 10:17 ` Julien Olivain via buildroot
2026-03-15 23:07   ` Petr Vorel [this message]
2026-03-16 10:53     ` Giulio Benetti
2026-03-16 10:54       ` Giulio Benetti
2026-03-16 21:28         ` Julien Olivain via buildroot

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=20260315230743.GB267706@pevik \
    --to=petr.vorel@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ju.o@free.fr \
    /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.