[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a76c1008-261d-5f0f-f739-e8cebf7610ac@al2klimov.de>
Date: Mon, 25 May 2020 20:32:48 +0200
From: "Alexander A. Klimov" <grandmaster@...klimov.de>
To: Joe Perches <joe@...ches.com>, Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: documentation
Am 25.05.20 um 20:24 schrieb Joe Perches:
> On Mon, 2020-05-25 at 20:01 +0200, Alexander A. Klimov wrote:
>> Does it matter whether I just feed the output of ...
>>
>> perl scripts/get_maintainer.pl --separator , --norolestats
>> 0001-Replace-HTTP-links-with-HTTPS-ones-documentation.patch
>>
>> ... into Git send-email To: prompt or actually CC: (not To:) mailing lists?
>
> Yes. vger mailing lists drop emails with large to:/cc:
> headers (It was >1024 chars, it may be different now)
Good to know.
>
> It's generally better to add --nogit --nogit-fallback to
> get_maintainer to avoid the git lookup addition of people
> that have modified files that aren't listed in MAINTAINERS.
Really? I used them for a previous version of my patch, but Jon (who
didn't use that params) complained about too many people not being CCed.
As Jon now applied (whatever branch on...) my patch, I assume that not
using those params is better.
After all not using them doesn't enlarge the set of recipients per patch
(of mine), but reduces patch size as I group changed files per set of
recipients.
>
> You could add a --bcc with those dropped names if you
> really want to have those people receive the emails.
>
Powered by blists - more mailing lists