[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2024020529-reproach-unleaded-d7a5@gregkh>
Date: Mon, 5 Feb 2024 05:14:53 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: stable@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [v6.7][PATCH 00/23] eventfs: Linus's updates for 6.7
On Sat, Feb 03, 2024 at 08:25:03PM -0500, Steven Rostedt wrote:
> On Sat, 03 Feb 2024 20:16:15 -0500
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > This is the update for 6.7. It includes Linus's updates as well as all the
> > patches leading up to them.
>
> Hmm, I just realized I didn't include the sha of the upstream commit. I
> simply ran the following command against v6.7.3:
>
> git log --reverse --no-merges --pretty=oneline v6.7..origin/master fs/tracefs/ | cut -d' ' -f1 | while read a; do if ! git cherry-pick $a; then break; fi ; done
>
> And I believe I removed one unrelated patch.
>
> I know that cherry-pick has a '-x' option that adds a: "(cherry picked from commit ...)"
> I can re-run it and make sure it still matches this branch if it makes
> it easier for you.
Please do, otherwise I have to dig out the sha1 "by hand" from the
original commits, which is a huge pain.
thanks,
greg k-h
Powered by blists - more mailing lists