[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023072507-smugness-landslide-bd42@gregkh>
Date: Tue, 25 Jul 2023 19:25:09 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: krzk@...nel.org, joe@...ches.com, geert@...ux-m68k.org,
netdev@...r.kernel.org, workflows@...r.kernel.org,
mario.limonciello@....com
Subject: Re: [PATCH] scripts: checkpatch: steer people away from using file
paths
On Tue, Jul 25, 2023 at 10:10:51AM -0700, Jakub Kicinski wrote:
> On Tue, 25 Jul 2023 18:53:48 +0200 Greg KH wrote:
> > > This script may break people's "scripts on top of get_maintainer"
> > > if they are using -f... but that's the point.
> >
> > Ok, I'll go fix up my local scripts,
>
> Which one? I spotted this in your repo but it already seems
> to use patches:
>
> https://github.com/gregkh/gregkh-linux/blob/master/scripts/generate_cc_list
Oh yeah, it does work on patches. Nevermind, I think I just use the -f
version manually when trying to figure out who to blame for a bug report
in a specific file :)
> How do you use this, BTW?
I do:
- git format-patch to generate the patch series.
- run the generate_cc_list script which creates XXXX.info files
(the XXXX being the patch number) that contain the
people/lists to cc: on the patch
- git rebase -i on the patch series and edit the changelog
description and paste in the XXXX.info file for that specific
patch.
Yeah, it's a lot of manual steps, I should use b4 for it, one of these
days...
thanks,
greg k-h
Powered by blists - more mailing lists