From: Jakub Kicinski <kuba@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>,
borisp@mellanox.com, saeedm@mellanox.com, leon@kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next 001/491] MELLANOX ETHERNET INNOVA DRIVERS: Use fallthrough;
Date: Thu, 12 Mar 2020 12:45:04 -0700 [thread overview]
Message-ID: <20200312124504.7ee481a9@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <cf74e8fdd3ee99aec86cec4abfdb1ce84b7fd90a.camel@perches.com>
On Wed, 11 Mar 2020 23:26:59 -0700 Joe Perches wrote:
> On Wed, 2020-03-11 at 23:23 -0700, David Miller wrote:
> > Joe, please use Subject line subsystem prefixes consistent with what would
> > be used for other changes to these drivers.
>
> Not easy to do for scripted patches.
> There's no mechanism that scriptable.
I have this to show me the top 3 prefixes used for files currently
modified in my tree:
tgs() {
local fs
fs=$(git status -s | sed -n 's/ M //p')
git log --oneline --no-merges -- $fs | \
sed -e's/[^ ]* \(.*\):[^:]*/\1/' | \
sort | uniq -c | sort -rn | head -3
}
You could probably massage it to just give you to top one and feed
that into git commit template?
next prev parent reply other threads:[~2020-03-12 19:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1583896344.git.joe@perches.com>
2020-03-11 4:51 ` [PATCH -next 001/491] MELLANOX ETHERNET INNOVA DRIVERS: Use fallthrough; Joe Perches
2020-03-11 7:01 ` Leon Romanovsky
2020-03-12 6:23 ` David Miller
2020-03-12 6:26 ` Joe Perches
2020-03-12 8:03 ` David Miller
2020-03-12 19:45 ` Jakub Kicinski [this message]
2020-03-12 19:52 ` Joe Perches
2020-03-11 4:51 ` [PATCH -next 002/491] MARVELL OCTEONTX2 RVU ADMIN FUNCTION DRIVER: " Joe Perches
2020-03-11 4:51 ` [PATCH -next 003/491] MELLANOX MLX5 core VPI driver: " Joe Perches
2020-03-11 7:00 ` Leon Romanovsky
2020-03-11 4:51 ` [PATCH -next 020/491] XEN HYPERVISOR INTERFACE: " Joe Perches
2020-03-11 6:47 ` Jürgen Groß
2020-03-11 4:51 ` [PATCH -next 027/491] AMD XGBE DRIVER: " Joe Perches
2020-03-11 4:51 ` [PATCH -next 028/491] BROADCOM BNX2X 10 GIGABIT ETHERNET " Joe Perches
2020-03-11 4:51 ` [PATCH -next 029/491] BROADCOM BNXT_EN 50 " Joe Perches
2020-03-11 4:51 ` [PATCH -next 030/491] BROADCOM GENET " Joe Perches
2020-03-11 16:35 ` Florian Fainelli
2020-03-11 4:51 ` [PATCH -next 031/491] BROCADE BNA 10 GIGABIT " 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=20200312124504.7ee481a9@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=borisp@mellanox.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
/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