From: Jakub Kicinski <kuba@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: krzk@kernel.org, joe@perches.com, geert@linux-m68k.org,
netdev@vger.kernel.org, workflows@vger.kernel.org,
mario.limonciello@amd.com
Subject: Re: [PATCH] scripts: checkpatch: steer people away from using file paths
Date: Tue, 25 Jul 2023 12:52:07 -0700 [thread overview]
Message-ID: <20230725125207.73387bfc@kernel.org> (raw)
In-Reply-To: <2023072507-smugness-landslide-bd42@gregkh>
On Tue, 25 Jul 2023 19:25:09 +0200 Greg KH wrote:
> 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...
Oh, neat! I do a similar thing. Modulo the number of steps:
git rebase --exec './ccer.py --inline'
I was wondering if I was the only one who pastes the Cc: person
into the patch, because I'd love to teach get_maintainer to do
the --inline thing, instead of carrying my own wrapper...
next prev parent reply other threads:[~2023-07-25 19:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230721062617.9810-1-boon.khai.ng@intel.com>
[not found] ` <20230721062617.9810-2-boon.khai.ng@intel.com>
[not found] ` <e552cea3-abbb-93e3-4167-aebe979aac6b@kernel.org>
[not found] ` <DM8PR11MB5751EAB220E28AECF6153522C13FA@DM8PR11MB5751.namprd11.prod.outlook.com>
[not found] ` <8e2f9c5f-6249-4325-58b2-a14549eb105d@kernel.org>
[not found] ` <20230721185557.199fb5b8@kernel.org>
[not found] ` <c690776ce6fd247c2b2aeb805744d5779b6293ab.camel@perches.com>
2023-07-25 1:04 ` [Enable Designware XGMAC VLAN Stripping Feature 1/2] dt-bindings: net: snps,dwmac: Add description for rx-vlan-offload Jakub Kicinski
2023-07-25 3:53 ` Joe Perches
2023-07-25 7:33 ` Geert Uytterhoeven
2023-07-25 13:19 ` Mario Limonciello
2023-07-25 13:43 ` Joe Perches
2023-07-25 14:37 ` Krzysztof Kozlowski
2023-07-25 15:59 ` [PATCH] scripts: checkpatch: steer people away from using file paths Jakub Kicinski
2023-07-25 16:53 ` Greg KH
2023-07-25 17:10 ` Jakub Kicinski
2023-07-25 17:25 ` Greg KH
2023-07-25 19:52 ` Jakub Kicinski [this message]
2023-07-25 21:01 ` Joe Perches
2023-07-25 16:57 ` Krzysztof Kozlowski
2023-07-25 21:18 ` Joe Perches
2023-07-25 22:15 ` Jakub Kicinski
2023-07-26 6:28 ` Joe Perches
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=20230725125207.73387bfc@kernel.org \
--to=kuba@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=krzk@kernel.org \
--cc=mario.limonciello@amd.com \
--cc=netdev@vger.kernel.org \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox