From: Greg KH <gregkh@linuxfoundation.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: does 548b8b5168c9 qualify for stable?
Date: Fri, 23 Oct 2020 16:22:31 +0200 [thread overview]
Message-ID: <20201023142231.GA2518006@kroah.com> (raw)
In-Reply-To: <4f1324d2-6b0f-dcb6-ff58-a6a05a15d407@rasmusvillemoes.dk>
On Fri, Oct 23, 2020 at 03:40:26PM +0200, Rasmus Villemoes wrote:
> Hi,
>
> Please consider whether
>
> commit 548b8b5168c90c42e88f70fcf041b4ce0b8e7aa8
> Author: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> Date: Thu Sep 17 08:56:11 2020 +0200
>
> scripts/setlocalversion: make git describe output more reliable
>
> qualifies for -stable. It removes one potential source of binary
> non-reproducibility that we have actually seen cause problems.
>
> I'm fine with it not qualifying, but please let me know if so, because
> then I'll go and add some workarounds to various customer projects.
>
> In case it doesn't cherry-pick cleanly (I think there might have been
> some shell-portability patches replacing $() by `` or something like
> that) I am happy to provide backports to the still maintained -stable
> branches.
Looks like it qualifies, how far back do you want it to go?
And yes, backported patches always make it much easier to apply :)
thanks,
greg k-h
next prev parent reply other threads:[~2020-10-23 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 13:40 does 548b8b5168c9 qualify for stable? Rasmus Villemoes
2020-10-23 14:22 ` Greg KH [this message]
2020-10-23 14:37 ` Rasmus Villemoes
2020-10-23 14:45 ` Greg KH
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=20201023142231.GA2518006@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@rasmusvillemoes.dk \
--cc=stable@vger.kernel.org \
/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.