From: Lukasz Stelmach <l.stelmach@samsung.com>
To: Joe Perches <joe@perches.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] get_maintainer: ignore "my" e-mail address
Date: Mon, 29 Nov 2021 22:47:40 +0100 [thread overview]
Message-ID: <dleftjwnkqab2b.fsf%l.stelmach@samsung.com> (raw)
In-Reply-To: <7a56a2431825bb71b76bb3e90d3ce0897596bd48.camel@perches.com> (Joe Perches's message of "Thu, 25 Nov 2021 09:01:30 -0800")
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
It was <2021-11-25 czw 09:01>, when Joe Perches wrote:
> On Thu, 2021-11-25 at 17:14 +0100, Lukasz Stelmach wrote:
>> It was <2021-11-16 wto 15:14>, when Joe Perches wrote:
>> > On Tue, 2021-11-16 at 22:34 +0100, Łukasz Stelmach wrote:
>> > > Ignore one's own e-mail address given as a parameter to --ignore-me
>> > > or in the EMAIL environment variable.
>> >
>> > Why is this useful?
>> >
>> > git send-email already supports this.
>> >
>> > --suppress-cc=<category>
>> > Specify an additional category of recipients to suppress
>> > the auto-cc of:
>> >
>> > • author will avoid including the patch author
>> >
>> > • self will avoid including the sender
>> >
>> > --[no-]suppress-from
>> > If this is set, do not add the From: address to the cc:
>> > list. Default is the value of sendemail.suppressFrom
>> > configuration value; if that is unspecified, default to
>> > --no-suppress-from.
>> >
>>
>> Not really, git send-email does not support --suppress-to, and with
>> get_maintainers.pl coupled with git send-email as follows
>>
>> --8<---------------cut here---------------start------------->8---
>> [sendemail]
>> tocmd = "`pwd`/scripts/get_maintainer.pl --nogit --nogit-fallback --norolestats --nol --"
>> cccmd = "`pwd`/scripts/get_maintainer.pl --nogit --nogit-fallback --norolestats --nom --nor --nofixes --"
>> --8<---------------cut here---------------end--------------->8---
>>
>> my address is added to To: if I am a maintainer of the patched files.
>> To avoid this the --ignore-me options can be added to tocmd.
>
> Rather than add complexity to the original get_maintainer script, is
> it possible to add a pipe like " | grep -v '<your_address>'" to tocmd ?
>
> I think it better to have these cmds use scripts ala:
>
> https://lore.kernel.org/all/1473862411.32273.25.camel@perches.com/
A thin wrapper is never a bad thing (-;
> And if not a script and the complexity is warranted (though I think not)
> I'd rather have something like --suppress-addresss "<addr>" added to
> get_maintainer.pl to allow one or more addresses to be suppressed.
Indeed, that sound a lot more reasonable. I'll probably go with wrappers
for now.
Thanks.
--
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2021-11-29 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211116213417eucas1p2a9679f03f7945f7c2bdfcba7a4e7c405@eucas1p2.samsung.com>
2021-11-16 21:34 ` [PATCH 1/2] get_maintainer: look for configuration files in ./scripts Łukasz Stelmach
[not found] ` <CGME20211116213417eucas1p133783708f01c8cf82bd341a4cf95a833@eucas1p1.samsung.com>
2021-11-16 21:34 ` [PATCH 2/2] get_maintainer: ignore "my" e-mail address Łukasz Stelmach
2021-11-16 23:14 ` Joe Perches
[not found] ` <CGME20211125161420eucas1p2b3dbac252dab05d0a5406d0fca8ab945@eucas1p2.samsung.com>
2021-11-25 16:14 ` Lukasz Stelmach
2021-11-25 16:33 ` Joe Perches
2021-11-25 17:01 ` Joe Perches
[not found] ` <CGME20211129214755eucas1p1c5ded52cda8d495d23dae59a871b9276@eucas1p1.samsung.com>
2021-11-29 21:47 ` Lukasz Stelmach [this message]
2021-11-16 21:56 ` [PATCH 1/2] get_maintainer: look for configuration files in ./scripts Andrew Morton
2021-11-16 23:10 ` Joe Perches
[not found] ` <CGME20211117120811eucas1p1cdc0aa3ab93d11cebf85592d4e98f0c7@eucas1p1.samsung.com>
2021-11-17 12:07 ` Lukasz Stelmach
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=dleftjwnkqab2b.fsf%l.stelmach@samsung.com \
--to=l.stelmach@samsung.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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
all inboxes | Powered by JetHome®