On Tue, Mar 23, 2021 at 12:05 PM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
The only time git gets involved is when we do a -rc release or when we do a "real" release, and then we use 'git quiltimport' on the whole stack.
Here's a script that I use (much too slow, I know), for checking this type of thing and I try to remember to run it before every cycle of -rc releases: https://github.com/gregkh/commit_tree/blob/master/find_fixes_in_queue
It's a hack, and picks up more things than is really needed, but I would rather it error on that side than the other.
Yes, my script is similar. Looks like yours also runs on a git tree.
I noticed that id_fixed_in runs `git grep -l --threads=3 <sha>` to find fixes; that's neat, I didn't know about `--threads=`. I tried it with ae46578b963f manually:
$ git grep -l --threads=3 ae46578b963f $
Should it have found a7889c6320b9 and 773e0c402534? Perhaps `git log --grep=<sha>` should be used instead? I thought `git grep` only greps files in the archive, not commit history?