From: Jakub Kicinski <kuba@kernel.org>
To: stsp <stsp2@yandex.ru>
Cc: netdev@vger.kernel.org,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowang@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tun: fix group permission check
Date: Mon, 9 Dec 2024 13:44:30 -0800 [thread overview]
Message-ID: <20241209134430.5cdefa09@kernel.org> (raw)
In-Reply-To: <062ab380-ee73-45ad-9519-e71bb3059c13@yandex.ru>
On Sun, 8 Dec 2024 09:53:40 +0300 stsp wrote:
> > I personally put a --- line between SOB and the CCs.
> > That way git am discards the CCs when patch is applied.
> >
> I simply used the output of
> get_maintainer.pl and copy/pasted
> it directly to commit msg.
> After doing so, git format-patch
> would put --- after CCs.
> How to do that properly?
You can have multiple --- markers, you can insert your marker and let
git format-patch add another.
next prev parent reply other threads:[~2024-12-09 21:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 7:36 [PATCH net-next] tun: fix group permission check Stas Sergeev
2024-12-05 16:50 ` Willem de Bruijn
2024-12-06 2:42 ` Jason Wang
2024-12-08 1:44 ` Jakub Kicinski
2024-12-08 1:44 ` Jakub Kicinski
2024-12-08 6:53 ` stsp
2024-12-09 21:44 ` Jakub Kicinski [this message]
2024-12-09 21:53 ` stsp
2024-12-08 1:50 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2024-11-17 9:05 Stas Sergeev
2024-11-17 15:04 ` Willem de Bruijn
2024-11-18 21:40 ` Willem de Bruijn
2024-11-19 10:51 ` Paolo Abeni
2024-11-19 10:54 ` stsp
2024-11-19 9:42 ` stsp
2024-11-19 14:56 ` Willem de Bruijn
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=20241209134430.5cdefa09@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stsp2@yandex.ru \
--cc=willemdebruijn.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.