From: Sasha Levin <sashal@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Backport dependencies helper
Date: Tue, 31 Mar 2020 10:08:30 -0400 [thread overview]
Message-ID: <20200331140830.GN4189@sasha-vm> (raw)
In-Reply-To: <20200331134400.GA24671@1wt.eu>
On Tue, Mar 31, 2020 at 03:44:00PM +0200, Willy Tarreau wrote:
>Hi Sasha,
>
>On Tue, Mar 31, 2020 at 08:32:17AM -0400, Sasha Levin wrote:
>> Each
>> directory represents a kernel version which we'll call K, and each file
>> inside that directory is named after an upstream commit we'll call C,
>> and it's content are the list of commits one would need to apply on top
>> of kernel K to "reach" commit C.
>
>That's very interesting! I still have nightmare-like memories or
>complete week-ends spent trying to address this using heuristics
>when I was maintaining 2.6.32 and 3.10. However how do you produce
>these ? Is this related to the stable-deps utility in your stable-tools
>repository ?
No, those tools try to do the same thing, but work differently.
stable-deps attempts to look at context lines surrounding the patch
itself to guess which other patches might be interesting.
While here, I use git-bisect to create a list of commits required to be
applied before any given commit.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-03-31 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 12:32 Sasha Levin
2020-03-31 13:44 ` Willy Tarreau
2020-03-31 14:08 ` Sasha Levin [this message]
2020-03-31 14:41 ` Willy Tarreau
2020-04-03 14:24 ` 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=20200331140830.GN4189@sasha-vm \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®